From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Em dash using Hoefler
Date: Tue, 20 Aug 2013 14:00:16 +0200 [thread overview]
Message-ID: <52135A50.1040104@wxs.nl> (raw)
In-Reply-To: <947CCEDB-7FCA-4A5D-97E4-DF17B48118AA@gmail.com>
On 8/20/2013 1:02 PM, Wolfgang Schuster wrote:
>
> Am 20.08.2013 um 11:52 schrieb Marco Patzer <lists@homerow.info>:
>
>> On 2013–08–20 Marco Patzer wrote:
>>
>>> On 2013–08–19 Martin Moncrieffe wrote:
>>>
>>>> Hopefully, this is the correct list for this question. I'm trying
>>>> to typeset documents using the font Hoefler on MacOSX (10.8.4)
>>>> with ConTeXt 2013.05.28 from the TeXlive 2013 distribution. All
>>>> works, but unfortunately, em dashes are not typeset correctly;
>>>> there are three dashes instead of a continuous line.
>>>
>>> The font (at least my version) does not contain an em dash in slot
>>> U+2014.
>>
>> I checked a different version of the font (1.000) and it works. It
>> seems you're using a version not containing an em dash.
>
> I can reproduce Martins problem but when I write – (Alt + -) and — (Alt + Shift + -)
> both symbols appear in the output.
>
> I checked the font (Hoefler Text.ttc on Mac OS 10.8.4) and it contains a emdash
> at slot 2014 but its named “emdash.standard”. There is also a character with
> the name “emdash” in the font at slot F0010.
great ... another non standard use of names ... in a few years open type
will be as big a mess as type one
you can play with:
local tlig = {
-- endash = "hyphen hyphen",
-- emdash = "hyphen hyphen hyphen",
[0x2013] = { 0x002D, 0x002D },
[0x2014] = { 0x002D, 0x002D, 0x002D },
-- quotedblleft = "quoteleft quoteleft",
-- quotedblright = "quoteright quoteright",
-- quotedblleft = "grave grave",
-- quotedblright = "quotesingle quotesingle",
-- quotedblbase = "comma comma",
}
in font-otc.lua (remake the format and wipe the font cache)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-20 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 10:20 Martin Moncrieffe
2013-08-20 8:33 ` Marco Patzer
2013-08-20 9:52 ` Marco Patzer
2013-08-20 11:02 ` Wolfgang Schuster
2013-08-20 12:00 ` Hans Hagen [this message]
2013-08-20 12:25 ` Khaled Hosny
2013-08-20 11:10 ` Martin Moncrieffe
2013-08-20 11:51 ` Marco Patzer
2013-08-20 12:00 ` Matt Gushee
2013-08-20 12:07 ` Martin Moncrieffe
2013-08-20 12:16 ` Hans Hagen
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=52135A50.1040104@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).