ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jeff Smith" <ascarel@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: XeTeX old style numerals
Date: Sat, 18 Oct 2008 20:47:18 -0400	[thread overview]
Message-ID: <2e8813a0810181747v73801ae1q48a32812febfb062@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00810181456x1da5b284q7bc2c85b49ffa83f@mail.gmail.com>

Thank you Mojca for this quick reply! I didn't expect one right away,
so I'm glad I'm not the only one not wanting to leave ConTeXt aside
even during the weekend. ;-) So tlig it is.

Thanks again!
Jeff

On Sat, Oct 18, 2008 at 17:56, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
> On Sat, Oct 18, 2008 at 11:19 PM, Jeff Smith wrote:
>>
>> \definefontfeature[bodyfeatures][method=node,script=latn,language=dflt,liga=yes,onum=yes,kern=yes,trep=yes,dlig=yes]
>>
>> I get the onum and dlig working with this, but, like I said, the trep
>> doesn't work. If I am not mistaken, it's this feature that makes the
>> apostrophe look like the comma. Am I right?
>
> Short answer: tlig, not trep.
>
> Long answer:
>
> See the folder fonts/misc/xetex/fontmapping.
>
> Hans invented tlig and trep as a short word for tex ligatures and tex
> replacements. That's still a bit unstable area of ConTeXt, but at the
> beginning it indeed included all the replacements and all the
> ligatures of Knuthian TeX. But that was too much for my taste (many
> useless conversions like `?, `! and all the quotation marks, as well
> as some really nasty ones as a side effect: it kept converting grave
> accent into quotation mark for example).
>
> With some consensus we decided to keep only three of them: endash,
> emdash and apostrophe. In LuaTeX these might still be split (tlig for
> endash and emdash and trep for apostrophe). In XeTeX it seemed to much
> overhaul to split three replacements into (three :) files, so I made
> only a single one: tlig.[map|tec]
>
> You can use it as "mapping=tlig" in plain XeTeX. What ConTeXt does is
> a conversion from "tlig=yes" into "mapping=tlig". trep used to map to
> tex-text (so did tlig) a while ago, now I guess that it doesn't do
> anything at all.
>
> I find it a bit unlucky situation that the behaviour is a bit
> different, but introducing a new file trep.map with only a single
> replacement would be even more weird & confusing to me.
>
> Mojca
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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-10-19  0:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 18:07 Mohamed Bana
2008-09-19 18:57 ` Mojca Miklavec
2008-09-20  2:09   ` Mohamed Bana
2008-09-20 10:49     ` Hans Hagen
2008-10-11 20:10       ` Mohamed Bana
2008-10-14 12:07         ` Wolfgang Schuster
2008-10-14 17:16           ` Mohamed Bana
2008-10-18 21:19           ` Jeff Smith
2008-10-18 21:56             ` Mojca Miklavec
2008-10-19  0:47               ` Jeff Smith [this message]
2008-10-19 15:31           ` Mohamed Bana
2008-09-21  5:44   ` Yue Wang
2008-09-21 16:01     ` 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=2e8813a0810181747v73801ae1q48a32812febfb062@mail.gmail.com \
    --to=ascarel@gmail.com \
    --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).