Re: [Aleph] OpenType-to-TeX and other musings...
Thank you Taco and Gábor for your valuable comments-)
Based on both of your comments, it seems that the most practical approach
in the short run is for Aleph (whose raison d`etre is more focused on the
short run->) is to just treat otf's like cid/enriched type1 fonts (a la
Latin Modern), which is what ConTeXt (and I guess LaTeX too) are already
doing (with smart encodings, etc.) The main thing that aleph offers on
this front is >256-glyph encodings. Simple otp's could provide switches to
turn on needed features (small caps, superiors, swashes, etc) in a large
font without clogging the system with multiple encodings (Occam's razor);
only a single encoding vector for the entire raw font would be needed. I
know that loading encodings in ConTeXt would certainly be a lot simpler-)
On Sat, 17 Dec 2005 06:13:21 -0700,
3) OpenType fonts, as Taco has already mentioned, have a declarative nature: they tell you what to do but not how to do it.
In the short run, for Aleph's purposes, these declarations and much/most/all of the metainfo can be treated as "suggestions" for the otp designer to consider in implementing things. There is no need to treat them as something "holy". Based on your comments and my other research, I will focus on enriched/CID type1 (which I guess is equivalent to cff-flavored opentype) font solution in my own work, and not worry about otf declarations for now. In the long run, of course, it would be great if a rewrite of Omega could execute a complete implementation of otf functionality. I wish dear Yannis and Gábor the very best in this regard! Best to all Idris -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Idris Samawi Hamid wrote:
In the short run, for Aleph's purposes, these declarations and much/most/all of the metainfo can be treated as "suggestions" for the otp designer to consider in implementing things. There is no need to treat them as something "holy".
in the near future pdftex will provide open type as well as hooks for input processing using lua, so you may as well end up rewriting your otp's in a more friendly language Hans
On Sun, 18 Dec 2005 07:16:31 -0700, Hans Hagen
In the short run, for Aleph's purposes, these declarations and much/most/all of the metainfo can be treated as "suggestions" for the otp designer to consider in implementing things. There is no need to treat them as something "holy".
in the near future pdftex will provide open type as well as hooks for input processing using lua, so you may as well end up rewriting your otp's in a more friendly language
At the risk of getting off topic: I know nothing about lua-) What makes it such a great tool? Why not just use, e.g., Ruby (less languages for me to learn->)? But you are quite right: the otp language is a real bear... Best Idris -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Idris Samawi Hamid wrote:
On Sun, 18 Dec 2005 07:16:31 -0700, Hans Hagen
wrote: In the short run, for Aleph's purposes, these declarations and much/most/all of the metainfo can be treated as "suggestions" for the otp designer to consider in implementing things. There is no need to treat them as something "holy".
in the near future pdftex will provide open type as well as hooks for input processing using lua, so you may as well end up rewriting your otp's in a more friendly language
At the risk of getting off topic: I know nothing about lua-) What makes it such a great tool? Why not just use, e.g., Ruby (less languages for me to learn->)?
well, there is google ... lua is - small, so no huge overhead and expanding library base - clever enough for the job needed - a well designed embedded language - fun
But you are quite right: the otp language is a real bear...
indeed, let'd get rid of it -) Hans
. . . Just out of curiosity, Hans, does this mean that pdftex will (in the near future;) natively support OpenType fonts, namely without having to go through all the TeX font installation trickery? Dave On Dec 18, 2005, at 6:16 AM, Hans Hagen wrote:
Idris Samawi Hamid wrote:
In the short run, for Aleph's purposes, these declarations and much/most/all of the metainfo can be treated as "suggestions" for the otp designer to consider in implementing things. There is no need to treat them as something "holy".
in the near future pdftex will provide open type as well as hooks for input processing using lua, so you may as well end up rewriting your otp's in a more friendly language
Hans
David Wooten wrote:
. . . Just out of curiosity, Hans, does this mean that pdftex will (in the near future;) natively support OpenType fonts, namely without having to go through all the TeX font installation trickery?
that's the idea; of course we need some tex specific things because we want to do more than open type supports, but in any case live should become more easy Hans
On Dec 19, 2005, at 11:58 AM, Hans Hagen wrote:
David Wooten wrote:
. . . Just out of curiosity, Hans, does this mean that pdftex will (in the near future;) natively support OpenType fonts, namely without having to go through all the TeX font installation trickery?
that's the idea; of course we need some tex specific things because we want to do more than open type supports, but in any case live should become more easy
That is indeed excellent news. David
participants (3)
-
David Wooten
-
Hans Hagen
-
Idris Samawi Hamid