On Sat, 6 Sep 2003, Anuradha Ratnaweera wrote:
Let me put this in a simple point form using a hypothetical example:
Now, if I want to render character 51 of X inplace of the composite
character 4001+4010, how should I proceed? Is there a way to map
unicode sequences to actual (physical)
On Thu, 7 Aug 2003, Mike FABIAN wrote:
Jungshik Shin [EMAIL PROTECTED] :
On Sat, 2 Aug 2003, Chisato Yamauchi wrote:
Have you seen CJK's *TYPICAL* fonts.dir of TrueType fonts?
It is following:
Not many people would be fond of tweaking fonts.dir/scale files
these days
On Sat, 9 Aug 2003, Jungshik Shin wrote:
On Fri, 8 Aug 2003, Pablo Saratxaga wrote:
That being said, it would be nice to have the ability to do
user-configuration
of glyph substitutions in gtk2; eg telling that when a given font is
choosen, then characters of range 0x00-0xff should
On Fri, 8 Aug 2003, Mike FABIAN wrote:
Jungshik Shin [EMAIL PROTECTED] :
On Thu, 7 Aug 2003, Mike FABIAN wrote:
It can be automatically generated. The /usr/sbin/fonts-config script
on SuSE Linux generates such TTCap entries automatically into the
make some people frustrated if it just
On Fri, 8 Aug 2003, Pablo Saratxaga wrote:
On Fri, Aug 08, 2003 at 06:59:43PM +0900, Chisato Yamauchi wrote:
But Gtk2 has not complete font-substitution mechanism.
Therefore, Gtk2 is insufficient in CJK environment.
GTk2, using pango, has builtin fontset mechanism.
(it is always
On Thu, 7 Aug 2003, Steve Sullivan wrote:
For example, the Terminal edit current profile gui shows
the Miriam font, but Miriam isn't listed by xfontsel or xlsfonts.
There are two separate font systems, the X11 core font system and
the client-side system with Xft/fontconfig. What you get
On Sat, 2 Aug 2003, Chisato Yamauchi wrote:
Although the pliability of handling such special fonts is also important,
non BMP plane in XLFD is now the most important problem. Confusion is
already seen such as linux-utf8 list. An official definition should be
indicated right now. Why has
On Wed, 9 Jul 2003, Yu Shao wrote:
Jungshik Shin wrote:
On Tue, 8 Jul 2003, Yu Shao wrote:
I don't get you here, the first version of the patch was made for Red
Hat 7.3, at that time we have to use Mozilla with X core font. Since
then the patch has been there almost unchanged
Hi,
I sent the following to James Su to seek his opinion, but it was bounced. Now
I'm sending to 1i8n and fonts list expecting him or other Chinese experts to
pick this up.
Jungshik
Hi,
Could you make a comment on
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=441?
On Tue, 10 Dec 2002, Anthony Fok wrote:
Thank you for bringing up this important issue.
I was assigned with the task of dealing with s p a c e d - o u t CJK
fixedPitch font issue in konsole.
In addition to Konsole, gnome-terminal, Mozilla-xft(for rendering
text/plain or a portion of html
On 10 Dec 2002, Juliusz Chroboczek wrote:
JS Even with this weakness, Xprint is by far the best printing
JS solution available at the moment for Mozilla under Unix/X11
JS because postscript printing module of Mozilla does not work very
JS well yet
JC Xprint might work for CJK fonts,
It
disabled Xprint in their Mozilla RPM.
Xft, Xprint and PS printing module can coexist in Mozilla without
much problem as far as I can tell. Perhaps, that blocking I mentioned
above may not be acceptable?
Jungshik Shin
P.S. I'm CCing to fonts list of XF86
On Sun, 1 Dec 2002, Jungshik Shin wrote:
While trying to make Mozilla-Xft support non-BMP characters with fonts
like CODE2001.TTF (with pid=3/eid=10 Cmap), I found that freetype
and Xft need a little change. Details are sent to linux-utf8 list
(http://mail.nl.linux.org/linux-utf8/2002-12
On Tue, 3 Dec 2002, Jungshik Shin wrote:
Attached is my patch(a bit revised) to extend XftTextExtents16 to
support UTF-16 and to fix a typo in fstr.c of fontconfig(which makes the
conversion from UTF-16 to UCS-4 not work correctly for characters in
Sorry I forogot to attach
Hi,
While trying to make Mozilla-Xft support non-BMP characters with fonts
like CODE2001.TTF (with pid=3/eid=10 Cmap), I found that freetype
and Xft need a little change. Details are sent to linux-utf8 list
(http://mail.nl.linux.org/linux-utf8/2002-12/msg0.html) and Bugzilla
On Tue, 22 Oct 2002, Keith Packard wrote:
Thank you for your explanation.
Around 12 o'clock on Oct 22, Jungshik Shin wrote:
1. get a pattern from an application(fontconfig client)
2. apply configuration-specified editing rules to the pattern.
For each font:
3. read in font
On Fri, 18 Oct 2002, Keith Packard wrote:
Around 7 o'clock on Oct 18, Jungshik Shin wrote:
For some unknown reason, 'New Gulim' is picked up by 'fontconfig' or 'Xft'
for a certain characters when CODE2000 is explicitly requested by
applications like Mozilla and gedit (via Pango) More
On Fri, 18 Oct 2002, Keith Packard wrote:
Around 12 o'clock on Oct 18, Jungshik Shin wrote:
One possible explanation is that Code2000 isn't marked as supporting 'ko'
in font-cache for some reason while Ngulim is.
This explanation only makes sense when those two chars are NOT
included
Since the release of a new CODE2000 font(by James Kass at
http://home.att.net/~jameskass) with glyphs for Hangul Jamos, I've
been trying to test how it works with various browsers. Mozilla
with direct access to truetype fonts works fine, but Mozilla
with Xft patch has a problem with
On Sat, 7 Sep 2002, Keith Packard wrote:
Around 9 o'clock on Sep 7, Jungshik Shin wrote:
I'm not sure adding U+115F/U+1160 to the blank glyph list is the best
way, but it works. Keith, could you consider this?
The blank glyph list is supposed to be filled with all of the Unicode
On Wed, 14 Aug 2002, Owen Taylor wrote:
The current Korean orthography looks like a combination
of KSC-5607.1987 with the complete Hangul Syllables
area of Unicode.
I'm sorry to be 'pedantic'. Strictly speaking, this way of talking
about Korean orthography (in terms of precomposed
On Wed, 14 Aug 2002, Owen Taylor wrote:
Jungshik Shin [EMAIL PROTECTED] writes:
On Wed, 14 Aug 2002, Owen Taylor wrote:
The current Korean orthography looks like a combination
of KSC-5607.1987 with the complete Hangul Syllables
area of Unicode.
I'm sorry to be 'pedantic
On Mon, 22 Jul 2002, Keith Packard wrote:
Around 8 o'clock on Jul 22, Brian Stell wrote:
Will there be a way to get the localized name using the ascii only name?
How about the other way around? Given a localized name+lang, would
it be possible to get the ascii name? Put differently,
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
On Mon, 8 Jul 2002, Keith Packard wrote:
Around 14 o'clock on Jul 8, Owen Taylor wrote:
+locale = (FcChar8 *)setlocale (LC_CTYPE, NULL);
Don't you mean LC_MESSAGES?
I believe it should be LC_CTYPE. Some people like me
have the following because English menu and (error) messages
On Sat, 29 Jun 2002, Jungshik Shin wrote:
On Fri, 28 Jun 2002, Keith Packard wrote:
I'm confused by this; my exposure to Chinese fonts says that simplified
Chinese and traditional Chinese have significant overlap in Unicode
codepoints, but that the glyphs are quite a bit different
On Sat, 29 Jun 2002, Keith Packard wrote:
Ooops. My message crossed yours in mail :-)
Around 9 o'clock on Jun 29, Jungshik Shin wrote:
IMHO, most problems with Han Unification arise not from using a _single_
font targeted at one of zh_TW/zh_CN/ja/ko to render a run of text in
another
to
agree with this. This is better than what I sent earlier. Just forgetting
about GB18030/GBK coverage and concentrating on GB2312 and Big5 coverage
is simpler as well as better.
Jungshik Shin
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org
28 matches
Mail list logo
