Korakurider,
I just saw the custom event translations in the new German po file. It looks as if the help text is not translated? Also, there seems to be a typo for "keyStroke" which you spelled "keystroke".
The relevant methods are senders of #addCustomEventFor:named:help:targetMorphClass : if anyone wants to take a look ...
- Bert -
On Wed, Apr 23, 2008 at 5:00 AM, Bert Freudenberg bert@freudenbergs.de wrote:
Korakurider,
I just saw the custom event translations in the new German po file. It looks as if the help text is not translated? Also, there seems to be a typo for "keyStroke" which you spelled "keystroke".
The relevant methods are senders of #addCustomEventFor:named:help:targetMorphClass: if anyone wants to take a look ...
Thanks for pointing out the bug. I attached additional patch transTriggers2-KR.cs to #6704. Now output of #explainStatusAlternatives can be translated properly with gettext.
# Is this too late for 3.0 release?
/Korakurider
On 23.04.2008, at 11:36, Korakurider wrote:
On Wed, Apr 23, 2008 at 5:00 AM, Bert Freudenberg <bert@freudenbergs.de
wrote: Korakurider,
I just saw the custom event translations in the new German po file. It looks as if the help text is not translated? Also, there seems to be a typo for "keyStroke" which you spelled "keystroke".
The relevant methods are senders of #addCustomEventFor:named:help:targetMorphClass: if anyone wants to take a look ...
Thanks for pointing out the bug. I attached additional patch transTriggers2-KR.cs to #6704. Now output of #explainStatusAlternatives can be translated properly with gettext.
# Is this too late for 3.0 release?
Not at all, we're just beginning the 3.0 work. This will be the version in OLPC update.2 which is not due for at least two months.
- Bert -
etoys-dev@lists.squeakfoundation.org