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: analyzing type-otf.tex
Date: Tue, 08 Apr 2008 10:13:34 +0200	[thread overview]
Message-ID: <47FB292E.3080506@wxs.nl> (raw)
In-Reply-To: <6faad9f00804070358y732172bv39fb3e1c5bd738fc@mail.gmail.com>

Mojca Miklavec wrote:
> Hello Hraban,
> 
> thanks for pointing this out.
> 
> To Hans: the \typescriptthree indeed needs to go out of those
> definitions (line 300 in type-otf).

hm, can you post the line? i have this

\starttypescript [serif] [adventor,bonum,cursor,heros,pagella,schola,termes]

> To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
> you will be able to extract any more than (theoretical limit of) 256
> glyphs from the Type1 font with XeTeX - character slots and font
> glyphs are in one-to-one correlation, so I doubt that you can access
> the glyphs outside of those 256 slots (unless you make tfm & map
> files, but that's probably the reason why one wants to use XeTeX - to
> get rid of that encoding mess). So: I guess that Latin-1 works, but
> encoding=uc is ignored anyway.

in mkiv no encodings are used, although when an encoding is specicified, 
some trickery takes place, for instance: texnansi-whatever becomes 
whatever and so, i.e. the encoding is removed and internally fonts are 
remapped onto unicode.

> type-xtx contains quite some "uc" leftovers, but I'm not sure if
> "fixing" them is a wise idea or not (backward compatibility).

i dunno either ... this may date from the time that not that many open 
type fonts were around, so we may consider dropping it (i.e. we kind of 
assume that xetex users use open type)

Hans

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  parent reply	other threads:[~2008-04-08  8:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 11:35 Henning Hraban Ramm
2008-04-06 12:37 ` Henning Hraban Ramm
2008-04-07 10:58   ` Mojca Miklavec
2008-04-07 18:22     ` Henning Hraban Ramm
2008-04-07 22:43       ` Mojca Miklavec
2008-04-07 22:50       ` Mojca Miklavec
2008-04-08  6:44         ` Wolfgang Schuster
2008-04-08  7:11           ` Henning Hraban Ramm
2008-04-08  7:25             ` Wolfgang Schuster
2008-04-08  7:53         ` Hans Hagen
2008-04-08  8:13     ` Hans Hagen [this message]
2008-04-08 10:39       ` Mojca Miklavec
2008-04-08 11:41         ` Hans Hagen
2008-04-08 20:30           ` Henning Hraban Ramm

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=47FB292E.3080506@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).