Arne GÃtje (éçè) wrote:
3. Varient selectors: OTF includes a feature in the GSUB table to
specify which glyphs should be used for which codepoint in a specific
region (simplified chinese, trad. chinese, japanese, etc.). Currently
OO.o is the only application supposed to support this feature.
I w
On Thu, 24 Mar 2005 13:13:37 +0800, Arne GÃtje (éçè) <[EMAIL PROTECTED]>
wrote:
> > Although DynaLab was the font foundry commissioned by the MOE to
> > create the new standard character shapes to be used in Taiwan, Arphic
> > also sells a font of standard character shapes the MOE would approve
>
> I only know of the CNS11643 standard, but the CCCII included much more,
> right?
Yes. IIRC, there are about 7 characters. Anyway, the main
developer has died before the project has been finished, and there was
no successor to complete (and the involved people have probably also
realized
On Thursday 24 March 2005 13:49, Werner LEMBERG wrote:
> > There had been efforts to create a charset in Taiwan in the 1980s,
> > which includes all known varients (more than 100,000 characters),
> > each one having a distinctive codepoint. The idea was to let the
> > input method engine handle th
> There had been efforts to create a charset in Taiwan in the 1980s,
> which includes all known varients (more than 100,000 characters),
> each one having a distinctive codepoint. The idea was to let the
> input method engine handle this. For example, you type 'gu3' for
> 'bone', select the bone
> Although DynaLab was the font foundry commissioned by the MOE to
> create the new standard character shapes to be used in Taiwan,
> Arphic also sells a font of standard character shapes the MOE would
> approve of. I bought my copy in Taiwan in Jan 2001.
Interesting. Which one?
I'm only aware
On Thursday 24 March 2005 10:30, Theron Stanford wrote:
> On Wed, 23 Mar 2005 10:10:53 +0800, Arne GÃtje (éçè)
<[EMAIL PROTECTED]> wrote:
> > Traditionally the characters have been written all the same way in
> > all CJK areas (China, Taiwan, Japan, Korea, Singapore, Vietnam).
>
> This is not true
On Thursday 24 March 2005 03:45, Jan Willem Stumpel wrote:
> > But not all fonts reflect those attitudes. Fonts develped in
> > Mainland China *have to follow the GB1830 standard*, so there
> > is no other option.
>
> So GB1830 is a standard for the actual appearance of the glyphs?
Yes, I don't kn
On Wed, 23 Mar 2005 10:10:53 +0800, Arne GÃtje (éçè) <[EMAIL PROTECTED]>
wrote:
> Traditionally the characters have been written all the same way in all
> CJK areas (China, Taiwan, Japan, Korea, Singapore, Vietnam).
This is not true. The shapes of many characters used in both China
and Japan di
Arne GÃtje (éçè) wrote:
Ok, I think I need to explain this a bit. [..]
Thanks very much for this clear explanation.
But not all fonts reflect those attitudes. Fonts develped in
Mainland China *have to follow the GB1830 standard*, so there
is no other option.
So GB1830 is a standard for the actual a
On Wednesday 23 March 2005 12:24, Greg Aumann wrote:
> Arne GÃtje (éçè) wrote:
> > I am following the Arphic style used in the Big5 fonts. However,
> > I'm experimenting with OTF features, like providing multiple
> > varients for different regions. The next release (scheduled for
> > March 27.) wil
Arne GÃtje (éçè) wrote:
I am following the Arphic style used in the Big5 fonts. However, I'm
experimenting with OTF features, like providing multiple varients for
different regions. The next release (scheduled for March 27.) will
contain the varients for the "bone" character. Currently I know on
On Wednesday 23 March 2005 04:16, Jan Willem Stumpel wrote:
> > In my Mozilla browser, both of these "é" glyphs appear as the
> > Chinese style, [..] Maybe you should use PNG graphics here in
> > addition to your Unicode text so everyone can see what the
> > (trivial) difference is.
>
> Did that.
ÎÏÎÏ 22/ÎÎÏ/2005, ÎÎÎÏÎ ÎÏÎÏÎ ÎÎÎ ÏÏÎ 20:09, Î/Î Jan
Willem Stumpel
ÎÎÏÎÏÎ:
> Simos Xenitellis ÎÎÏÎÏÎ:
> > 1. [..]
>
> Unfortunately I do not know anything about Indic languages and
> scripts.
The link I mentioned (http://anakin.ncst.ernet.in/~aparna/consolidated/)
should be a good read for thi
> On Tuesday 2005.03.22 21:09:06 +0100, Jan Willem Stumpel wrote:
> >[..]
> >It's an interesting document what you are writing and I am would
> >interested to see how it progresses.
>
> Would it be a good idea to convert this into a wiki? No single
> user can know enough about the various langua
Edward H. Trager wrote:
You should mention the newer "Un" series of Korean fonts
announced by Jungshik Shin in September, 2003.
Thanks! I'll put that in shortly.
In my Mozilla browser, both of these "é" glyphs appear as the
Chinese style, [..] Maybe you should use PNG graphics here in
addition to y
Simos Xenitellis ÎÎÏÎÏÎ:
1. [..]
Unfortunately I do not know anything about Indic languages and
scripts.
2. You mention that "[IIIMF] has zero documentation". The choice of
words is not elegant.
You are quite right. It is rude. I changed it to âit is rather
short on user-level documentationâ, wh
> Jan Willem Stumpel wrote:
>
> > Would like to get comments & criticism especially about the
> > âinputâ part:
> >
> > http://www.jw-stumpel.nl/stestu.html#T6.3
Hi, Jan,
A few comments on your web page:
(1)
> 4.3 Korean
> For Korean, the free Baekmuk ttf fonts can be used. They are enormous i
ÎÏÎÏ 21/ÎÎÏ/2005, ÎÎÎÏÎ ÎÎÏÏÎÏÎ ÎÎÎ ÏÏÎ 18:36, Î/Î
Jan Willem Stumpel
ÎÎÏÎÏÎ:
> Would like to get comments & criticism especially about the
> âinputâ part:
>
> http://www.jw-stumpel.nl/stestu.html#T6.3
1. There are scripts the have a different "class" of complexity than
CJK, typically the Indic
Would like to get comments & criticism especially about the
‘input’ part:
http://www.jw-stumpel.nl/stestu.html#T6.3
Regards, Jan
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
20 matches
Mail list logo
