[Seaside] Re: [Pharo-users] i18n tools
panu.j.m.suominen at gmail.com
Mon Sep 13 05:52:33 UTC 2010
2010/9/12 Philippe Marschall <philippe.marschall at gmail.com>:
> I see what you mean. The other question is of course whether Magritte
> would work with a LazyTranslation where a String is expected.
It only passes the strings along. It does not do any operations to them.
At least I haven't bumbed in to a case where it would alter the string.
But of course this behaviour might change but then translating the text
would also be a problem.
Could you think something that might get broken in the future? I think
is vulnerable to calls that alter and copy the string, but in many
cases it would
brake the current translation system also.
> Maybe a better way would be a method
> like #markForLaterTranslation that would answer the receiver but also
> export it into the .po file?
It is other possibility and I thought it also. I see couple of problems.
If markForLaterTranslation does not mark the object in any way it
would be hard to determine in which cases text should be translated.
This can create situation
where text gets no translation or gets translated twice or more.
It requires quite many changes to code. User interface code has to be
changed to take care translations. And when translation logic is
changed the user interface code has to be changed too.
For example when arguments are added to translations #translate:
-method of seaside has to be changed too. I think this will divide the
logic to several places.
More information about the seaside