Re: gettext usage in libraries



On Thu, 29 Nov 2001, Bill Haneman wrote:

> Sander Vesik wrote:
> > 
> > On 27 Nov 2001, Ulrich Drepper wrote:
> > 
> > > Havoc Pennington <hp redhat com> writes:
> > >
> > > > Ulrich presumably means either a) all users should use a UTF-8 locale
> > > > or b) all apps should use locale encoding, not UTF-8. Though I've
> > > > failed to read his mind in the past.
> > >
> > > And you fail again.  Nobody here seems to understand what the gettext
> > > code does.  Unless the environment is broken (which isn't normally the
> > > case anymore and if it is can be fixed in the support code) the
> > > functions know what conversion to make.  Explicitly setting the
> > > charset is unnecessary at best and most of the time a big nuisance.
> > > The translator must have the choice as to which charset to use (there
> > > are still some languages which cannot be represented in Unicode) and
> > > the user must be able to run the application in whatever locale is
> > > best.  The gettext functions handle every situation just fine without
> > > bind_textdomain_codeset calls.
> > >
> > 
> > If the language cannot be represented in unicode then the language is
> > already in big trouble due to practicly exlcusive use of unicode...
> 
> I don't know of *any* examples of this among existing written "primary"
> languages.  Please give an example of a language that has neither an
> approved nor a proposed unicode code page...
> 

Uhhh... unicode isn't even really complete for something as widely used as
Tamil.

> ??
> 
> -Bill
> 

	Sander

"I don't think there is intelligent life within our solar system"
	-- Brian Behlendorf




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]