Re: [NTG-context] Unicode.otf

luigi scarso wrote:

On Jan 11, 2008 4:29 PM, Hans Hagen wrote:

...

Arthur Reutenauer wrote:

...

...

Is there another solution other than fontforge ? Sure, just rename the font to Unicode.ttf. And the problem should be fixed now, so try the next beta with the original name as well.

...

I mean using by using characters.data in char-def.lua:

[0x25C9] = { unicodeslot=0x25C9, category='so', description='FISHEYE' },

it should be easy with a bit \ctxlua get glyph by description . I guess you're better off preparing the inverse mapping and storing it in advance, otherwise you would be losing a lot of time because you would have to loop over characters.data to find the character you want. already taken care of ...

characters.context.unicodes characters.context.utfcodes characters.context.enccodes

are references to the big table (there are more tables) I think something like this

-- begin -- save this in symbols.lua Symbols={['BOX DRAWINGS LIGHT HORIZONTAL'] = 9472,

wel, we can make a characters.context.descriptions but i'm not sure if it will really be used, because when one knows this rather verbose string (has looked it up), one could as well use the (also found) unicode directly ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------