From: "Paul Schalck" <schickele@web.de>
To: <ntg-context@ntg.nl>
Subject: Palatino Linotype under MKIV
Date: Tue, 29 Jun 2010 11:15:42 +0200 [thread overview]
Message-ID: <E509C6D54AD944269C87500CA5F5DA07@netbook> (raw)
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Hi,
I'm trying to use the full glyph range of the Palatino Linotype font shipped
with XP (version 1.40; significantly different from the Windows 7 one) under
MKIV. Everything works fine (oldstyle figures, sups for instance), except
that the small cap "i" character has a dot whereas it shouldn't.
Here's a test file. The result, produced on WinXP / ConTeXt beta 2010-06-23,
is attached.
\definefontfeature[palatinolt-default][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality]
\definefontfeature[palatinolt-smcp][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,smcp=yes,onum=yes]
\definefontfeature[palatinolt-sups][mode=node,script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,sups=yes]
\starttypescript[serif][palatinolt][name]
\usetypescript[serif][fallback]
\definefontsynonym[Serif][file:pala.ttf][features=palatinolt-default]
\definefontsynonym[SerifBold][file:palab.ttf][features=palatinolt-default]
\definefontsynonym[SerifItalic][file:palai.ttf][features=palatinolt-default]
\definefontsynonym[SerifBoldItalic][file:palabi.ttf][features=palatinolt-default]
\definefontsynonym[SerifCaps][file:pala.ttf][features=palatinolt-smcp]
\stoptypescript
\definetypeface[palatinolt][rm][serif][palatinolt][default]
\setupbodyfont[palatinolt]
\enableprotruding\setuppagenumbering[location=]
\starttext
{\sc \input knuth }
\stoptext
As far as I can see, it has to do with the messy name list of the glyphs.
Both the normal small cap i and the small cap dotted i are named "i.sc", but
the wrong one is picked when the smcp feature is activated. Moreover, the
small cap glyphs have no unicode numbers in this font, so I cannot pick them
manually with \char"XXXX or even with \charXXXXX.
Any ideas how I can get the right dottless i?
[-- Attachment #2: palatinolt_mkiv_test.pdf --]
[-- Type: application/pdf, Size: 31368 bytes --]
[-- Attachment #3: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2010-06-29 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 9:15 Paul Schalck [this message]
2010-06-30 7:33 ` Taco Hoekwater
2010-06-30 7:46 ` luigi scarso
2010-06-30 16:16 ` Paul Schalck
2010-08-06 7:20 ` Vnpenguin
2010-08-06 7:24 ` Hans Hagen
2010-08-06 8:02 ` Vnpenguin
2010-08-06 10:34 ` Hans Hagen
2010-08-06 11:40 ` Vnpenguin
2010-08-06 11:46 ` Hans Hagen
2010-08-06 11:49 ` Vnpenguin
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=E509C6D54AD944269C87500CA5F5DA07@netbook \
--to=schickele@web.de \
--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).