[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Encoding problems with i18n() and kdbgstream (KDE 3.1rc2)
From:       Jonathan Singer <jsinger () genome ! wi ! mit ! edu>
Date:       2002-11-29 16:32:24
[Download RAW message or body]

> Furthermore, the "Add Translation..." dialog in KDevelop doesn't even offer
> en_US (only en_GB) as translation target, seemingly it supposes that every
> application is written in English.
> 
> Is this just a shortcoming of KDevelop or does KDE/QT l10n demand by desing
> that original messages always be in (US-)English?

If you're planning to put the project into the KDE CVS, please use US
English for translatable strings, function and variable names and comments.
It makes things much easier for translators, documentation writers and means
that in the absence of a translation, users reliably get English texts.

We appreciate that this is difficult for many developers, but if you notify
the kde-doc-english mailing list, someone will be happy to edit, proofread
or generally clean up whatever you've written. The earlier you let us know,
the better the job we can do. 

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]