#5023 HIGH Update.: tokenized Calculate.pot
Zarro Boogs per Child
bugtracker at laptop.org
Sat Nov 24 06:49:44 EST 2007
#5023: tokenized Calculate.pot
----------------------------------+-----------------------------------------
Reporter: xavi | Owner: rwh
Type: defect | Status: new
Priority: high | Milestone: Update.1
Component: calculator-activity | Version:
Resolution: | Keywords: i18n Pootle
Verified: 0 |
----------------------------------+-----------------------------------------
Comment(by xavi):
The main blocker right now is that there's '''no''' text to translate
given that there's nothing in:
* the POT (either as comments or otherwise),
* the source code (either as comments or otherwise),
* the en.po (as valid 'translation')
The simplest solution (albeit the most inefficient) would be to populate
the en.po with the intented text so that a translator can check for it
manually.
Another alternative would be to regenerate the POT adding the intended
text as comments.
Another issue would seem to be that there are two kinds of strings: user &
log.
User messages are obviously intended to be translated, but it's not always
the case for log messages, which depend on the visibility and target
audience of them. I'm no expert on the subject, but remember reading that
these log messages are better left as two clear segments: id & text. The
id part is non-translateable while the text is. This helps everybody by
allowing a more universal bug-reporting & debugging scheme: user,
developer and anybody else know they are referring to the same 'error_id'
but the text is local, allowing them to solve it locally without needing
to get 'foreign language support' that shuffles back-and-forth trying to
discover what the actual error is (due to the translation of the error
message).
--
Ticket URL: <http://dev.laptop.org/ticket/5023#comment:6>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list