Great! Thanks for the explanation and the pointers, I'll look into it. I see that a lot of code is already there, that's a huge relief for me :)
Best regards Richo
On Wed, Apr 28, 2010 at 3:34 AM, Korakurider korakurider@gmail.com wrote:
Hi Ricardo. I haven't noticed this requirement is covered in the GSoC project. Here are starting point.
- Background In Etoys image translation support based on gettext emulation has
been implemented. (You need to know basic concept of gettext; see http://www.gnu.org/software/gettext/)
+ POT Extraction: see class comment of GetTextExporter2 + Translation Engine: see #translated and
NaturalLanguageTranslator/GetTextTranslator
- Problem Current implementation is that all strings belong to the
textdomain "etoys". By this huge number of strings (>4000) are included in one big PO/POT and translators have difficulty to translate it. We need to divide it to a few text domains with appropriate size and inclusion criteria/packaging scheme.
Actually the translation framework have feature to mark class
category for some text domain. (review class side of TextDomainManager) But this has not been used because:
- We haven't got agreement on what division would be good
- There is risk that the framework cannot decide correct textdomain
in some case. (see #translated)
- So we couldn't implement the division in timeline of the past project.
- Related problem
SQ-139 in etoys bug tracker.
/Korakurider
On Wed, Apr 28, 2010 at 11:27 AM, Ricardo Moran richi.moran@gmail.com wrote:
Hi guys, I'm starting to work on the translation support for GSoC and since I know nothing of how it is implemented and I'm already delayed in the timeline
I
wanted to ask you if you have any pointers on what/where should I look. Thanks in advance! Richo _______________________________________________ etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev