eToys localizers may know that Dr. Geo (maintained by Hilaire Fernandes) has been integrated as a module in eToys, but as a new module it has not been as extensively localized as other eToys PO files (see DrGeoII-Core.po in the eToys project).<br>
<br>What you may *not* know is that an earlier version (and it's localization) has been hosted for some time upstream.<br><br><a href="http://l10n.gnome.org/module/drgeo/">http://l10n.gnome.org/module/drgeo/</a><br><br>
There have been enough subtle changes in the strings (slight rewording, capitalization, punctuation, etc.) that an automated merge of the upstream and local files fails to harvest as many of the strings as a human-mediated copy/paste effort can accomplish (with the Mark One pattern recognition engine of eye and brain). By opening these two files in separate windows. a great deal of localization can be accomplished quickly with copy/paste (with careful attention to subtle changes). This is a valid approach as the context of the strings is essentially conserved (Dr. Geo) and it is unlikely to result in mistaking the intended meaning of a potentially ambiguous string.<br>
<br>A native speaker will be able to quickly harvest several hundred strings in much less time than it would take to type them using the suggested *thoughtful* copy/paste method. Of course, this opportunity flows both ways, as there may be strings translated in our DrGeoII-Core.po that are not complete in the upstream PO file and you can have a two-for-one impact by contributing back upstream using the upstream's process (claiming the PO file for translation, downloading and localizing it, submitting it for review and commit as an attachment via the package's page in your language project).<br>
<br>This approach can help to bring our eToys project that much closer to completion, every string counts. Thank you for attention to this matter.<br><br>cjl<br><br>