FreeTDS Development Group

[ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>]

> 
> > For Spanish in Spain, LANG=es_ES.  
> 
> Or sometimes es_ES@euro.
> 

Or en_US.UTF-8. Full syntax should be lang AT modified.charset but I didn't
find a good documentation on this subject...
RH8 use utf8 by default... (I think cause gnome2 support utf8 without
problem)

> > [es_ES]
> >     date format = %b %d %Y %I:%M%p
> >     language = spanish
> >     char set = iso_1
> 
> Is there such a thing as iso_15 in the char set list (for 
> iso-8859-15)?
> 
> > I said that the value of LANG was controlled by ISO 
> standards.  That's not
> > quite true.  It *should* be controlled that way, but some 
> OS vendors use
> > different values.  We have no way to cope with that except by adding
> > sections to locales.conf for every conceivable key.  Also, the
> > setlocale(3) function is standardized by ANSI, so we should use that
> > instead of reading the LANG variable directly.  
> 
> Well, I think we should be able to get rid of locales.conf 
> altogether in
> the long run, and just use libc i18n facilities to figure 
> everything out
> from the locale.  I've started work in this direction, but it needs
> polishing before I'm ready to commit it.
> 

I think we do not support very well language....
- language should be send to server at connect time (not supported on
TDS7/8)
- collation is not supported (on either TDS7 and TDS8)
- single-byte are never translated
- we do not send correct server charset (how to know charsets supported by
server? iso-8859-15 is quite new so I don't think is widely supported...)
- date are parsed only with english format (see convert.c)

"select * from master.dbo.syscharsets" and "select * from
master.dbo.syslanguages" can help... 

I discovered some day ago that language in TDS7/8 must be sended at login
with local name (not greek but greek written in greek)

But this stuff are 0.62... I think we should divide i18n: 
- charset and encoding
- formatting (date, numbers)

freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================