<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Webdings;
        panose-1:5 3 1 2 1 5 9 6 7 3;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Verdana",sans-serif;
        color:#1F497D;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
.MsoChpDefault
        {mso-style-type:export-only;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">That’s very impressive … I would have thought much more complex changes would be needed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The only problem is that the search-replace operations will break if we ever change any of the wording in the UI. Which I do, frequently
(not being good at getting these things perfect first time)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">This has been the root cause of my reluctance to make the CQPweb UI multilingual. It’s not the difficulty of creating the initial translation(s)
– it’s the difficulty of keeping all of the translations up to date as the system evolves…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">best<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Andrew.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">PS. You’ve got most of the text used in the bibg HTML chunks, but this may miss some things: e.g. text generated by client side JavaScript
e.g. in jsc/cword.js or jsc/categorise.js *, or the query-heading strings generated by QueryRecord::print_solution_heading(). I guess the former probably don’t make much difference to your users - but the latter is another powerful reason for not going multilingual
as it would create word-order problems for assembling the sentence-bits. Not only raw strings, but also concatenation action ordering, would need to be customised.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">* See<o:p></o:p></span></p>
<p class="MsoNormal"><img width="701" height="252" style="width:7.302in;height:2.625in" id="Picture_x0020_1" src="cid:image001.png@01D3997C.67006570"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cwb-bounces@sslmit.unibo.it [mailto:cwb-bounces@sslmit.unibo.it]
<b>On Behalf Of </b>"Andrés Chandía"<br>
<b>Sent:</b> 28 January 2018 03:41<br>
<b>To:</b> CWBdev Mailing List <cwb@sslmit.unibo.it><br>
<b>Subject:</b> [CWB] Translation<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I want to share with you guys the scripts I used to translate CQPWeb into Spanish (CL).<br>
I know you probably can make better scripts, faster, for sure that Perl can improve it, but anyway here I send it for you to take profit and if you want use it as you like....<br>
<br>
I haven't written instructions but here I comment a little:<br>
<br>
the directory with the scripts has to be at the same level of the cqpweb directory<br>
the translation directory is called "translateCQPweb", so you cd into it<br>
and then you run the script "sh translate.sh" <br>
<br>
If you want to use it to translate to some other language you will have to go along all of the other scripts replacing the spanish version for the one you need, always be careful to scape metacharacters like ( | [ etc. in your language translation. Files
containing translations are these ones:<br>
<br>
3pluswords.sh<br>
boldtrans.sh<br>
buttonstrans.sh<br>
codeupdate.sh<br>
italictrans.sh<br>
optiontrans.sh<br>
quotetrans.sh<br>
radchkbxtrans.sh<br>
shorttrans.sh<br>
<br>
finally edit the "translate.sh" file and follow the instructions that this one does have<br>
<br>
I wanted to add a log for each command that tells the command and the "error" if there is one to the log, but I couldn't find the way.<br>
<br>
There are some words that can not be translated this way, so those ones have to be translated manually, like in some places the words "Description", "Delete" and some others.<br>
<br>
I have my Chilean Spanish version of CQPWeb in here: <a href="http://www.chandia.net/iecmap">
http://www.chandia.net/iecmap</a><br>
<br>
and the file with all the translations in here: <a href="http://www.chandia.net/compart/translateCQPweb.7z">
translateCQPweb.7z</a> <br>
<br>
I hope you can use it in further development.<br>
<br>
Thanks!<br>
<br>
_______________________<br>
andrés chandía<br>
<a href="http://www.chandia.net" target="_blank"><span style="text-decoration:none"><img border="0" id="_x0000_i1025" src="http://mail.chandia.net/images/chandia_net.png" alt="chandia.net"></span></a><a href="https://twitter.com/andreschandia" target="_blank"><span style="text-decoration:none"><img border="0" width="20" height="20" style="width:.2083in;height:.2083in" id="_x0000_i1026" src="http://mail.chandia.net/images/ico_tw.png"></span></a><br>
<a href="http://chandia.net/content/nmt" title="Unificador ortogràfico de mapudungun">NMT</a> |
<a href="http://chandia.net/content/dungupeyem" title="Analizador y generador mofológico de
mapudungun">
Dungupeyem</a> | <a href="http://corlexim.cl" title="Corpus lexicográfico de
mapudungun">
Corlexim</a><br>
<br>
administrador de:<br>
<a href="http://parles.upf.edu">Parles.upf</a> | <a href="http://amindterapia.com">
Amind terapia</a> | <a href="http://koyaktumapuche.net">ONG Mapuche koyaktu</a> |
<a href="http://parles.upf.edu/llocs/nocando">Nocando</a> | <a href="https://iac.upf.edu">
IAC</a> | <a href="https://iac.upf.edu/cddz">CddZ</a> | <a href="https://iac.upf.edu/isac">
ISAC</a> | <a href="https://catcg.upf.edu">CatCg</a> |<br>
mail: <a href="http://mail.corporacionkoyaktu.net">ONG Mapuche koyaktu</a> | <a href="http://mail.psicoaching.net">
Psicoaching</a> |<br>
<span style="font-size:18.0pt;font-family:Webdings;color:#4F6228">P</span> <span style="font-size:10.0pt">
No imprima innecesariamente. ¡Cuide el medio ambiente!</span><o:p></o:p></p>
</div>
</body>
</html>