Translation problems; possible solution

[Martin Preuss]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Thursday 23 October 2003 12:10, A. Alper ATICI wrote:
> On Thu, Oct 23, 2003 at 10:49:12AM +0200, Christian Stimming wrote:
> > And by the way *if* msgid's are extended to make them unambiguous, then
> > the mangling extension should be added as a *prefix*.
>
> Well, decorate the names as you wish.
That doesn't have anything to do with decoration ;-)
It is just easier to just move a char* pointer forward as compared to 
replacing the string by something else (which would also imply a quite 
complicated string management).

[...]
> I understand demangling code is necessary to deal with "C" locale, cases
> where gettext is not installed. But, my whole idea is based on creating
> minimal burden for programmer now and in future. If you'll end up doing
> some fancy string parsing and/or creating wizard wrapper functions, then
> I'm ready to pull my vote, let the translators be doomed.
That might pose minimal burden onto the developer (which I'm not sure of) but 
it is very unpleasant for people whose locales are not working for any of the 
following reason (feel free to add items):
- - no gettext installed
- - users locale not set up
- - users locale not supported (i.e. po file missing)

With your approach the user would see something like "new at 001".
Hmm, doesn't look too good to me ;-)

So I must conclude that I like Christian's idea better, because from the 
developers point of view the additional work is quite the same as with your 
approach (just need to insert a descriptive string to the item, the macros 
will do the rest) while there are far less problems for the desktop user...


kind regards
Martin

- -- 
LibChipcard - http://www.libchipcard.de
OpenHBCI - http://www.openhbci.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/l7UhwcZBcYAOyGYRAna6AJwI8R3SakHkFQBTosXkD1uNRHp95ACeMuWX
1vJ424Zpqcx9hNyLyi4rNUw=
=tI5o
-----END PGP SIGNATURE-----