ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unicode.otf
Date: Fri, 11 Jan 2008 16:29:42 +0100	[thread overview]
Message-ID: <47878B66.8020400@wxs.nl> (raw)
In-Reply-To: <20080111152246.GC21098@phare.normalesup.org>

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)



-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-01-11 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11  2:26 Unicode.otf luigi scarso
2008-01-11  4:03 ` Unicode.otf Arthur Reutenauer
2008-01-11  4:51   ` Unicode.otf luigi scarso
2008-01-11 15:22     ` Unicode.otf Arthur Reutenauer
2008-01-11 15:29       ` Hans Hagen [this message]
2008-01-11 17:46         ` Unicode.otf luigi scarso
2008-01-11 21:03           ` Unicode.otf Hans Hagen
2008-01-11 21:47             ` Unicode.otf Arthur Reutenauer
2008-01-11 22:09           ` Unicode.otf Arthur Reutenauer
2008-01-11 15:55       ` Unicode.otf luigi scarso
2008-01-11 18:15         ` Unicode.otf Arthur Reutenauer
2008-01-12  0:02           ` Unicode.otf luigi scarso
2008-01-12  3:21             ` Unicode.otf Arthur Reutenauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47878B66.8020400@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).