still looking for marking string for translation
stéphane ducasse
ducasse at iam.unibe.ch
Mon Feb 20 09:18:01 UTC 2006
hilaire
you are right. A dictionary per package is needed.
This is also an indication that having first class package would help
to attach to them resources.
(argh I do not have the time to look at that). I will try to dig into
what alex did to introduce
first class packages and see how far he was.
Stef
On 20 févr. 06, at 09:52, Hilaire Fernandes wrote:
> Bert Freudenberg a écrit :
>> Am 19.02.2006 um 20:50 schrieb Hilaire Fernandes:
>>>>> http://minnow.cc.gatech.edu/squeak/402
>>> The only localisation system I know is gettext, in this system the
>>> string to translate are marked directly in the source code (with a
>>> special function as _()). Next, such marked strings can be
>>> grouped in
>>> the translation file for the translator.
>>>
>>> I was thinking about something to get the same effect (i.e. get the
>>> string ready to be translated)
>> Just send #translated, as mentioned on the wiki page above.
>
> Yes, this I already know but it is not sufficient. As Yoshiki
> suggested I also need to add each string in the translation
> dictionnary.
>
> What would be helpfull is to have a separate translation
> dictionnary for each package.
>
> As far as I can understand, there is for now one big dictionnary to
> record the string for translation (NaturalLanguageTranslator
> allKnownPhrases).
>
> Hilaire
>
>
>> - Bert -
>
>
> --
> ADD R0,R1,R2,LSL #2
>
More information about the Squeak-dev
mailing list
|