Around 13 o'clock on Jul 10, Anthony Fok wrote:
I have been wondering: would OpenType technology be able to help solve this
issue, since OpenType allows multiple glyphs (for different target
language) for each character?
Not any better than the OS/2 codePageRange bits that we already have;
Hi,
[As a disclaimer, I have only followed this discussion from afar, and my
reply may actually be off-topic. If this is the case, please disregard
my post ! I'm just trying to advocate the importance of oe ligature
here :) ]
While I've never seen ñ in my limited exposure to French, I don't
On Tue, Jul 09, 2002 at 11:06:46PM -0700, Keith Packard wrote:
Around 13 o'clock on Jul 10, Anthony Fok wrote:
I have been wondering: would OpenType technology be able to help solve this
issue, since OpenType allows multiple glyphs (for different target
language) for each character?
On Tue, Jul 09, 2002 at 11:00:58PM -0700, Keith Packard wrote:
Around 13 o'clock on Jul 10, Anthony Fok wrote:
Just to clarify the current situation: while the GB18030 encoding covers
the entire Unicode codepoints, the current GB18030 standard does not
mandate or specify any characters
On Tue, Jul 09, 2002 at 06:09:01PM -0700, Keith Packard wrote:
Around 18 o'clock on Jul 9, Jungshik Shin wrote:
a) call setlocal (LC_ALL, ) myself?
I'm afraid this can have an unexpected side effect, which could
surprise/upset some application program developers.
Keith Packard [EMAIL PROTECTED] writes:
Agreed; this choice was somewhat rhetorical in nature...
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
Keith Packard wrote on 2002-07-10 01:09 UTC:
AFAIK, SUS and POSIX say
that it's implementation-dependent.
Too bad the POSIX spec is closed so I can't check.
For all of you who haven't heard yet, SUS3 and POSIX:2001 are now the
same thing and are freely available online on
On Wed, 10 Jul 2002, Marius Gedminas wrote:
On Tue, Jul 09, 2002 at 06:09:01PM -0700, Keith Packard wrote:
Around 18 o'clock on Jul 9, Jungshik Shin wrote:
b) use $LANG or $LC_CTYPE?
If this road is taken, it has to be determined which env.
variables have to be
Around 21 o'clock on Jul 8, Patrice =?ISO-8859-15?B?SOlk6Q==?= wrote:
not requiring the ? to be included in default font selection would lead
people that don't particularly configure their font selection mechanism to
be unable to read properly written French texts.
It's important to
On Wed, Jul 10, 2002 at 01:55:34PM -0400, Jungshik Shin wrote:
POSIX fixes the order to LC_ALL, then LC_CTYPE, then LANG.
Could you quote the part of SUS3/POSIX where this rule is fixed
as you wrote.
http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html:
The values
Around 4 o'clock on Jul 10, Owen Taylor wrote:
As far as the question at hand; I think that giving up and using a
default value or no value is fine if setlocale() hasn't been
called. But I don't see any problems with checking
LC_ALL/LC_CTYPE/LANG... it might be a nice touch.
Given that
Yao Zhang wrote:
...
The only way to find out which Han variant one font has is by
looking at it.
When you say looking at it do you mean actually having a
human view the glyphs?
As long as we can configure it properly, zh_CN, zh_HK and zh_TW
etc really do not matter.
What do you
12 matches
Mail list logo
