ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unicode.otf
Date: Fri, 11 Jan 2008 05:03:50 +0100	[thread overview]
Message-ID: <20080111040350.GB21098@phare.normalesup.org> (raw)
In-Reply-To: <fe8d59da0801101826y11d14769vd82d0c16331cefdf@mail.gmail.com>

  This seems to be a slight misfeature in Mark IV: I take that when
opening a font file with an .otf extension, it assumes it is an OpenType
font with PostScript outlines (cubic splines); when the file has a .ttf
extension, it supposes there are TrueType outlines (quadratic splines).
Both types of outlines are mutually exclusive and are contained in
different tables of the font file (respectively, 'CFF' and 'glyf').
This is indeed a widespread convention (including FontForge's), but this
font doesn't follow it, since it has TrueType outlines and an .otf
extension; hence the error message (ConTeXt is looking for a CFF table
and can't find it, since there is a glyf table instead).

  When you edited the font in Fontforge and exported it as
UnicodeSymbols.otf, it was converted to a CFF-based OpenType font, so
ConTeXt could use it.

  I consider this a bug in Mark IV (I think the problem is really in
ConTeXt, not LuaTeX).  It should be able to use the original font, even
if this extension thing is annoying.

> And How can I quicky  access symbols like U+25c9 ?

  One would think you knew that, Luigi!  Just use ^^^^25c9, for example.

	Arthur
___________________________________________________________________________________
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  4:03 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 ` Arthur Reutenauer [this message]
2008-01-11  4:51   ` Unicode.otf luigi scarso
2008-01-11 15:22     ` Unicode.otf Arthur Reutenauer
2008-01-11 15:29       ` Unicode.otf Hans Hagen
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=20080111040350.GB21098@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --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).