From: Oliver Buerschaper <oliver.buerschaper@mpq.mpg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeTeX "tex-text" mapping problem
Date: Mon, 12 Feb 2007 14:28:08 +0100 [thread overview]
Message-ID: <BD22D325-8D88-47B0-BC9F-1322AF08A72F@mpq.mpg.de> (raw)
In-Reply-To: <45D04B86.8070503@wxs.nl>
>> Hi all,
>>
>> there seems to be a problem with the XeTeX engine and the
>> "mapping:tex-text" feature for OpenType fonts. Try this:
>>
>> ---
>>
>> \usetypescriptfile[type-minion]
>> \usetypescript[minion][uc]
>> \setupbodyfont[minion,13pt]
>>
>> \starttext
>> There is --- without any doubt --- a tiny problem.
>> \stoptext
>>
>> ---
>>
>> together with the attached typescript file. Unfortunately, "---" is
>> not replaced by an em dash :-( Substituting works flawlessly for
>> plain
>> XeTeX examples. Of course, replacing "---" with the proper Unicode em
>> dash in the above source solves the problem (by avoiding it).
>>
>> Any hints as to what I've done wrong?
> what is mapping=tex-text supposed to do?
As far as I understood it's supposed to map TeX character sequences
like "--" or "---" onto the corresponding Unicode characters. In fact
these sequences aren't necessary at all, one could easily type the
appropriate Unicode dashes in the source code. However, for the
source editor I use a monospaced font which makes it rather hard to
distinguish those proper Unicode dashes. I guess the character
substitution that "mapping=tex-text" performs will extend to few
other TeX sequences as well ... but definitely not for accented
characters. Perhaps
http://scripts.sil.org/cms/scripts/page.php?
site_id=nrsi&item_id=xetex_faq#ligs
might be helpful.
Oliver
prev parent reply other threads:[~2007-02-12 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 9:46 Oliver Buerschaper
2007-02-12 11:12 ` Hans Hagen
2007-02-12 13:14 ` Mojca Miklavec
2007-02-12 13:28 ` Oliver Buerschaper [this message]
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=BD22D325-8D88-47B0-BC9F-1322AF08A72F@mpq.mpg.de \
--to=oliver.buerschaper@mpq.mpg.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).