You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Erik Huelsmann <e....@gmx.net> on 2005/02/26 10:07:04 UTC

gettext string translation in libsvn_fs_*/tree.c

Just a little question:

Did we agree to mark all error strings for translation? 

Background: Both libsvn_fs_base and libsvn_fs_fs have a (large?) number of
untranslatable error messages, yet in their tree.c files some *have* been
marked. 

bye,

Erik.

-- 
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gettext string translation in libsvn_fs_*/tree.c

Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.

On Wed, 2 Mar 2005, [UTF-8] Branko �^Libej wrote:

> Erik Huelsmann wrote:
>
> >>Just a little question:
> >>
> >>Did we agree to mark all error strings for translation?
> >>
> >>Background: Both libsvn_fs_base and libsvn_fs_fs have a (large?) number of
> >>untranslatable error messages, yet in their tree.c files some *have* been
> >>marked.
> >>
> >>
> >
> >Ok. I remember again:
> >
> >We decided to translate all output (including errors), except those which
> >travel over the network.
> >
> >This means that all libraries can translate their messages, but server
> >applications should prevent setting LC_MESSAGES to anything but "C"/"POSIX".
> >
> >Am I correct here?
> >
> >
> How on earth can we force a particular locale in mod_dav_svn? That would
> affect avary other Apache module running on the same server, and that's
> horrible.
>
Yeah, and it seems hard to force gettext to not translate in svnserve as
well, at least on platforms without LC_MESSAGES. Maybe it is better to
just punt on this and document that you need to setup your locale
correctly to not get translated messages to the client.

Even if we could turn off translation in our libs (by modifying the _()
macro, for example), we can't force other libraries to not translate. So
you might always get a translated message from libc, for example.

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org


Re: gettext string translation in libsvn_fs_*/tree.c

Posted by Branko Čibej <br...@xbc.nu>.
Erik Huelsmann wrote:

>>Just a little question:
>>
>>Did we agree to mark all error strings for translation? 
>>
>>Background: Both libsvn_fs_base and libsvn_fs_fs have a (large?) number of
>>untranslatable error messages, yet in their tree.c files some *have* been
>>marked. 
>>    
>>
>
>Ok. I remember again:
>
>We decided to translate all output (including errors), except those which
>travel over the network.
>
>This means that all libraries can translate their messages, but server
>applications should prevent setting LC_MESSAGES to anything but "C"/"POSIX".
>
>Am I correct here?
>  
>
How on earth can we force a particular locale in mod_dav_svn? That would 
affect avary other Apache module running on the same server, and that's 
horrible.

-- Brane



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gettext string translation in libsvn_fs_*/tree.c

Posted by Erik Huelsmann <e....@gmx.net>.
> "Erik Huelsmann" <e....@gmx.net> writes:
> 
> > Ok. I remember again:
> >
> > We decided to translate all output (including errors), except those
> which
> > travel over the network.
> >
> > This means that all libraries can translate their messages, but server
> > applications should prevent setting LC_MESSAGES to anything but
> "C"/"POSIX".
> >
> > Am I correct here?
> 
> I don't know, but we should document it somewhere, even if only in the
> code.  What's the problem with sending translated error messages over
> the network?  Is it to avoid giving the client translations that don't
> match the client's locale?  Is it a problem with the encoding of the
> translations?

The problem is mainly with a server running a different language than the
client. But inherently, the client may be running his locale with a
characterset which is unable to (readably) display characters from the error
message.

bye,


Erik.

-- 
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gettext string translation in libsvn_fs_*/tree.c

Posted by Philip Martin <ph...@codematters.co.uk>.
"Erik Huelsmann" <e....@gmx.net> writes:

> Ok. I remember again:
>
> We decided to translate all output (including errors), except those which
> travel over the network.
>
> This means that all libraries can translate their messages, but server
> applications should prevent setting LC_MESSAGES to anything but "C"/"POSIX".
>
> Am I correct here?

I don't know, but we should document it somewhere, even if only in the
code.  What's the problem with sending translated error messages over
the network?  Is it to avoid giving the client translations that don't
match the client's locale?  Is it a problem with the encoding of the
translations?

-- 
Philip Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gettext string translation in libsvn_fs_*/tree.c

Posted by Erik Huelsmann <e....@gmx.net>.
> 
> Just a little question:
> 
> Did we agree to mark all error strings for translation? 
> 
> Background: Both libsvn_fs_base and libsvn_fs_fs have a (large?) number of
> untranslatable error messages, yet in their tree.c files some *have* been
> marked. 

Ok. I remember again:

We decided to translate all output (including errors), except those which
travel over the network.

This means that all libraries can translate their messages, but server
applications should prevent setting LC_MESSAGES to anything but "C"/"POSIX".

Am I correct here?


bye,

Erik.

-- 
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org