[texworks] Scripting: applyTranslation()

Paul A Norman paul.a.norman at gmail.com
Sun Jan 16 00:24:33 CET 2011

Thanks Stefan,

I must have been interrupted when doing Turkish - I was in the process of

I assume that local speakers will know their own code,  the extra
information is for people who are not native speakers of the code(s) who,
while scripting, and working from English, are given extra information so
that they can know for sure what they are handling.
Also to help when there is more than one contender for the code or it is not
clear as in nl for Dutch, nl does not suggest Dutch directly, en (usa?)
hence Euro style (UK),  pl does not need any detail really. Will need to add
an entry for Persian - fa - afain not obvious in English.

And of course the two contenders for Portuguese - we have the Brazilian
version of Portuguese apparently.

es - Many English speakers are not aware of the language situation on the
Iberian peninsular and looking at the map, lump it all simplistically as
Spanish, which is not the situation -have  put  Castilian in the 3rd column
for consistency.


On 16 January 2011 03:18, Stefan Löffler <st.loeffler at gmail.com> wrote:
> Hi,
> On 2011-01-13 12:30, Paul A Norman wrote:
>> P.S. Here is a better layout in the draft.
> Yeah, the list is looking good. But you seem to have missed tr (Turkish).
> In addition, I have two questions:
> 1) Why is "Castilian" in the second column, while e.g. Brazilian is in
> the third?
> 2) Is there any reason you give native names (or transcriptions thereof,
> as for Chinese) for some languages? Seeing that the whole manual is in
> English, I'd assume the prospective readership should be familiar with
> the English names. If not, it would probably be best to give native
> names (ideally non-transcribed) for all languages.
> Cheers,
> Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/texworks/attachments/20110116/dcca4866/attachment.html>

More information about the texworks mailing list