You said in a French translation feat.req. comment :
"My idea is to simply generate a Python source file containing all the
texts from the XML files so it will integrate with current translation
process."
I see possibles shortcoming :
The strings from xml tech files aren't actually gettext-ed (no _( in the code). Don't know is it's feasible.
The .po will grow largely, this may slow down the UI (i don't know how well gettext scale)
break the code/data separation (i know, this one is purely formal :) )
On the other hand, having localized Rules dir could be problematic : need more logic to include the right one (if any), synchronization, need to use another translation software to handle xml (xml2po miss the name attribute).
My 2 cents.
Yann Cantin
A4FEB47F
--
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've translated some tech desc (in TL1.xml), including the name attribute, and the gui crash with :
File "/home/yann/.ospace/coyote.ysoft.org_9080_client_/ige/log.py", line 95, in debug
print str(item),
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 16: ordinal not in range(128)
The code (at least in the logger) isn't utf8-proof for the techtree portion.
--
Yann Cantin
A4FEB47F
--
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1328873
Originator: NO
You said in a French translation feat.req. comment :
"My idea is to simply generate a Python source file containing all the
texts from the XML files so it will integrate with current translation
process."
I see possibles shortcoming :
The strings from xml tech files aren't actually gettext-ed (no _( in the code). Don't know is it's feasible.
The .po will grow largely, this may slow down the UI (i don't know how well gettext scale)
break the code/data separation (i know, this one is purely formal :) )
On the other hand, having localized Rules dir could be problematic : need more logic to include the right one (if any), synchronization, need to use another translation software to handle xml (xml2po miss the name attribute).
My 2 cents.
Yann Cantin
A4FEB47F
--
Logged In: YES
user_id=1328873
Originator: NO
Doing some testing, i run into a problem :
I've translated some tech desc (in TL1.xml), including the name attribute, and the gui crash with :
File "/home/yann/.ospace/coyote.ysoft.org_9080_client_/ige/log.py", line 95, in debug
print str(item),
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 16: ordinal not in range(128)
The code (at least in the logger) isn't utf8-proof for the techtree portion.
--
Yann Cantin
A4FEB47F
--