xliff-inline — archive

Inline code SC Meeting - June-14

From: Arle Lommel
To: [email protected]
Date: Tue, 14 Jun 2011 19:11:00 -0000

In line with today's discussion, I wanted to share an example of a complex inline code I found before the meeting: <p>© 2011 Localization World   <span class= style21 > +1 208 263 8178</span>   <script type= text/javascript > /* <![CDATA[ */ function hivelogic_enkoder(){var kode= kode= nrgh@%>,**=,40kwjqho1hgrn+wDudkf1hgrnBkwjqho1hgrn?l+.{@hgrn\000,l+ + wDudkf1hgrn.,4.l+wDudkf1hgrn@.{~,[email protected]>,40kwjqho1hgrn+?l>3@l+uri>**@{>_%@{g + hnr,\000+fghFrduFkrpiuj1lqwu@V{.;>45.@,f?3+fli6>,0+lDwghFrdufkh1rg@n~f.,l + .k>jwhq1oghnrl?3>l@u+ir*>@*>{~_%__kCuj3q33/____.ijkIugxInuslxm4otzxCY~1>A7 + 81C/iB6.iol9A/3.oGzjkIugxink4ujCq\001i1/o1nAmzkt4rjkquoB6AoCx.lu-AC-A~\0 + 01(nFxm6t662b1lmnLxj{Lqxvo{p7rw}{F\\\0014AD:;4F2lE91lro<D261rJ}mnLxj{lq + n7xmFt4l332____44Dr}qwpunn7xmEtDrF91rx{Do00\001F+D5GJ.;myHo{p:~x3{33z____ + u{m\00066b6xuomx{{LzrJuh.<Aq==x7=\000b.\177Ih\177\177xm,oh.{y:oxp{~33 + ____3{z\000u6m66ubmx{oLxr{uz{Fx\000mu.yIhqrt~m,.Hq4u\0003~33:____z\000 + yqo\001p{F+mntxC(jkqu@_%__ghnr_%@hgrn%>nrgh@nrgh1vsolw+**,1uhyhuvh+,1mrlq + +**, ;x='';for(i=0;i<kode.length;i++){c=kode.charCodeAt(i)-3;if(c<0)c+=12 + 8;x+=String.fromCharCode(c)}kode=x ;var i,c,x;while(eval(kode));}hivelogic_enkoder(); /* ]]> */ </script> </p> This is from the LocalizationWorld website and has a <script> tag embedded in a <p>, as you can see. In this case, you could hide this from the translator with no negative consequence, but consider the following (from https://github.com/maqetta/maqetta/issues/79 ): <span dojoType= dojo.data.ItemFileWriteStore jsId= jsonStore data= {"identifier":"id", "label": "label", "items": [ { "id":"AF","label":"<b>IMx</b>", "type":"continent"}, { "id":"AR","label":" <div class="aaaa" ", "type":" country " } ] } > Presumably this could appear in something going to XLIFF the content of the inline tag contains potentially localizable content (see the blue bit)? It shows that there are cases where discarding or hiding the content of inline markup in XLIFF would create problems. On the other hand, I wouldn't want to expose more translators to either of the cases above. So I'm not sure what the best solution is: you can't live with it and you can't live without it. (I know, ideally there would have been an internationalization process that would have externalized the localizable content in the second example, but we know that won't always happen in the real world.) Best, Arle