SteveKing schrieb:
>If we don't set the thread locale, then the Subversion messages won't
>show up correctly. Subversion uses gettext, and gettext determines which
>translated strings to use depending on the locale set.
>
>
All this multi-language-codepage-locale-conversion stuff gives me a
headache.
>It will only fail if they run TSVN in english (or another non-native
>language). If they set the correct language in the settings, it would
>have worked. (And it also was reported that it works then).
>
>
Problem is that this combines the application's appearance (language of
messages) with the application's function (code page and encoding),
which I do not really like.
>If you have an idea on how to force gettext to use a specific language
>and not the one set by the thread locale, we could get rid of that...
>
>
I have never looked at gettext, so I do not know.
I see a few options here:
* Let TortoiseProc use the default locale, and encapsulate every
subversion call that might returns errors with a SetThreadLocale()
function pair (and possibly the callbacks as well).
* Set the code page as you do now, but do not use any windows or library
function that might rely on the current locale. That would mean never
mix CStringA and CStringW, or do the conversions manually.
* Leave everything as it is now ... until the next person complains
Can't we force everyone to use unicode? Developing for non-western
laguages can give you the creeps!
Norbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 18 22:29:46 2005