From divanov at aha.ru Sat Mar 1 05:52:02 2008 From: divanov at aha.ru (Dmitriy Ivanov) Date: Sat, 1 Mar 2008 08:52:02 +0300 Subject: [cl-typesetting-devel] Re: [cl-pdf-devel] Character encoding? References: <47C1DA36.7020101@gigamonkeys.com> <47C1DAD7.9050606@gigamonkeys.com><47C26093.7070102@gigamonkeys.com><47C3180B.9050403@fractalconcept.com> <47C3A829.3030709@gigamonkeys.com><000001c87851$d493f6d0$8100a8c0@digo> <47C891E2.2090106@fractalconcept.com> Message-ID: <000001c87b6e$d06c32f0$8100a8c0@digo> Marc Battyani wrote on Sat, 01 Mar 2008 00:14:42 +0100 02:14: | Right but I still think that glyphs substitution is a cl-typesetting | issue. | | Sure, the simple unicode to non-unicode conversion could be just an | encoding issue but even that can be more complex. For instance you | could gather the unicode glyphs used in a document and dynamically | generate a custom non-unicode encoding that maps them to a font glyphs | if you have less than 256 glyphs and they are all in the font. | | Doing more than just the simplest encoding conversions can only be done | at the cl-typesetting level. For instance if a font lacks the euro | glyph, cl-typesetting could substitute a custom cl-pdf box that draws | the euro sign. There are also the ligatures, the ellipsis (... ?) etc. Substituting such a box with a custom font and encoding would be a nice feature. But IMHO, we can approach it after introducing an advanced style system equipped with font families. -- Sincerely, Dmitriy Ivanov lisp.ystok.ru