The real unresolved issue with gettext is handling server side stuff.
In the client we just use the process environment variables (through
setlocale). In client libraries we use the process environment
variables, the including program decision of calling setlocale or not,
but we change the "domain".
In server side libraries (or libraries which are both server and client
side) we are ok with the domain thing but, where do we take the language
settings from? Different connected users will have different locale
needs, there's a need to address that. The problem is that the current
gettext runtime depends on setlocale, and this function does not allow
for a thread to have different settings than the rest of the process.
This will mean that in a threaded Apache we would disturb other threads
if we call setlocale.
We need to have a...
"char *dlgettext(char *domain, char *language, char *msgid)"
Solutions:
1) Modify gettext runtime and include it in a directory.
2) Modify gettext runtime and get the modified version included upstream.
2) Write our own code for accessing the .mo files.
The SVN protocol should be modified so that the client send the locale
preferences to the server. In the DAV version the solution is to use
HTTP's "Accept-Language". Doing this will provide the added benefit of
serving localized content to web browsers wandering through the
repository, as every browser nowadays sends the "Accept-Language" header.
What do you think about these issues?
Bye, Nico.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 30 20:53:21 2004