Re: Implementing Complex Unicode Scripts

2001-02-26 Thread John H. Jenkins
At 10:57 AM -0800 2/26/01, jgo wrote: > > Doing complex character-to-glyph mapping involving > > the OpenType tables is another matter. My understanding is that the MacOS >> can do the former, but cannot yet do the latter. > >Well, the Apple folks who should know are on the list, so let's ask

Re: Implementing Complex Unicode Scripts

2001-02-26 Thread jgo
> The OpenType font format is supported; that means that the OS can read the > files, do *basic* (i.e. 1:1) character-to-glyph mapping, and rasterize the > glyph outlines. This is as much as is involved in supporting plain-vanilla > TrueType fonts, only with additional possibilities for what form

Re: Implementing Complex Unicode Scripts

2001-02-21 Thread Antoine Leca
Apurva Joshi va escriure: > > Re: "Uniscribe is just an implementation of these specifications, and I hope > sincerely Microsoft will not hide some "features" into USP10.DLL in order to > kill any concurrence." > > The process of adding new feature support to Uniscribe is not unlike adding > new

RE: Implementing Complex Unicode Scripts

2001-02-20 Thread Apurva Joshi
ts all features that usp10.dll uses. Thanks, -apurva -Original Message- From: Antoine Leca [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 20, 2001 9:20 AM To: Unicode List Cc: Unicode List Subject: Re: Implementing Complex Unicode Scripts Charlie Jolly wrote: > > Fonts: &g

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread John H. Jenkins
At 9:17 AM -0800 2/20/01, Charlie Jolly wrote: >Thanks for the comments thus far. > >They have helped clarify alot of ambiguities. > >As for AAT, could Apple not supply template fonts so that font designers can >concentrate on the glyphs. I.e. replace master glyphs with their own. > It's on our t

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Peter_Constable
On 02/20/2001 11:19:48 AM Antoine Leca wrote: >Yes. Font technologies does not allow things like Nagari or Sinhala rendering >to operate by themselves, they need some assistance from the underlying >platform. >This is the current state of art, one may hope it will change in the future. I don't

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread John Hudson
At 09:17 AM 2/20/2001 -0800, Charlie Jolly wrote: >As for AAT, could Apple not supply template fonts so that font designers can >concentrate on the glyphs. I.e. replace master glyphs with their own. The folk at Apple are certainly aware that they have a problem with AAT's current level of 'tech

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Peter_Constable
On 02/20/2001 10:19:37 AM John Hudson wrote: >The Apple AAT and SIL Graphite approach work a little differently. I'm not >familiar enough with Graphite to know how they handle stuff like character >reordering, or how difficult it is to achieve such things in their Graphite >Description Language,

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Antoine Leca
Charlie Jolly wrote: > > Fonts: > Do fonts have to tie themselves to a script engine. Yes. Font technologies does not allow things like Nagari or Sinhala rendering to operate by themselves, they need some assistance from the underlying platform. This is the current state of art, one may hope it

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Charlie Jolly
Thanks for the comments thus far. They have helped clarify alot of ambiguities. As for AAT, could Apple not supply template fonts so that font designers can concentrate on the glyphs. I.e. replace master glyphs with their own. Charlie Jolly

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread John Hudson
At 04:21 AM 2/20/2001 -0800, Charlie Jolly wrote: >Do fonts have to tie themselves to a script engine. Will an Opentype font >for lets say Hindi such as MS Mangal work on an Apple OS or Linux? Or is >this font tied to Uniscribe? If this is correct then shouldn't there be a >better solution? Mang

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread John H. Jenkins
At 4:21 AM -0800 2/20/01, Charlie Jolly wrote: >Do fonts have to tie themselves to a script engine. Will an Opentype font >for lets say Hindi such as MS Mangal work on an Apple OS or Linux? Or is >this font tied to Uniscribe? If this is correct then shouldn't there be a >better solution? Both OT

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Peter_Constable
On 02/20/2001 08:13:08 AM "Brendan Murray/DUB/Lotus" wrote: >It can: the OpenType specification is just that - Open. The original >TrueType spec was created with Apple, so my guess is that at least Windows >and MacOS can process OpenType fonts. OpenType and TrueType are not the same: OpenType i

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Peter_Constable
On 02/20/2001 06:21:09 AM "Charlie Jolly" wrote: >Should an open source script processing engine be part of the standard? As I >understand it if you want to develop Unicode solutions for complex scripts >then you either have to do it yourself or rely upon Uniscribe or ATSUI. Whether or not the

Re: Implementing Complex Unicode Scripts

2001-02-20 Thread Brendan Murray/DUB/Lotus
"Charlie Jolly" <[EMAIL PROTECTED]> wrote: > Does anybody know if there is a chart or table showing what OS's, > Applications, Programming Languages support Unicode and in particular what > scripts? You'll find some of this on http://www.unicode.org/unicode/onlinedat/products.html. > Should an o

Implementing Complex Unicode Scripts

2001-02-20 Thread Charlie Jolly
Does anybody know if there is a chart or table showing what OS's, Applications, Programming Languages support Unicode and in particular what scripts? Should an open source script processing engine be part of the standard? As I understand it if you want to develop Unicode solutions for complex scr