Re: [Fonts]Re: [I18n]Using current locale in font selection

[Keith Packard]

Around 13 o'clock on Jul 9, Erik van der Poel wrote:

 Not that you need any more input to make this decision, but there is
 some precedent to go with LC_CTYPE too: the X Consortium went with that
 for both text output and keyboard input in their i18n work circa X11R5.

Ok, so now what do I do with applications which haven't called 
setlocale (LC_ALL, )?  Do I:

a)  call setlocal (LC_ALL, ) myself?
b)  use $LANG or $LC_CTYPE?
c)  Ignore the locale information and leave the
font language preference unset?

Keith PackardXFree86 Core TeamHP Cambridge Research Lab


___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

Re: [Fonts]Re: [I18n]Using current locale in font selection

[Jungshik Shin]

On Tue, 9 Jul 2002, Keith Packard wrote:

 Ok, so now what do I do with applications which haven't called
 setlocale (LC_ALL, )?  Do I:

   a)  call setlocal (LC_ALL, ) myself?

  I'm afraid this can have an unexpected side effect, which could
surprise/upset some application program developers.

   b)  use $LANG or $LC_CTYPE?

  If this road is taken, it has to be determined which env.
variables have to be refered to in what order. AFAIK, SUS and POSIX say
that it's implementation-dependent. Since XF86 is used with many OS',
it'd be best to follow the 'local' convention. Then, I don't know how
to figure it out without calling setlocale(LC_CTYPE,). In case of Glibc,

If $LC_ALL is set, use it
else if $LC_CTYPE is set, use it
else if $LANG is set,  use it.

   c)  Ignore the locale information and leave the
   font language preference unset?

  This might well be the best course along with documenting
that setlocale() should be called to make font matching/selection locale
dependent or that better still is to explicitly provide lang info when
invoking font selection APIs.

  Jungshik

___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts