ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: active strings in luatex?
Date: Mon, 14 Jan 2008 01:20:40 +0100	[thread overview]
Message-ID: <20080114002040.GI5056@phare.normalesup.org> (raw)
In-Reply-To: <6faad9f00801130638l253bd3b8le102527953a61f7b@mail.gmail.com>

> XeTeX always converts, say, c + combining caron into a ccaron whenever
> one exists in the font

  Does it really?  I had understood from the last discussion on the
XeTeX list that it did not, with the example of capital alpha +
combining breathing which was not set correctly.  But maybe it's LaTeX's
fault?

>                                    In the case of LM, the font has
> combining characters with zero width with the accent shifted to the
> left, so that it looks OK on an average glyph

  That's a nice trick, but in the case of 'l', it looks really ugly.

>                                               (but in general, TeX
> does a better job with combining characters) unless one requests two
> accents.

  Sure.

> So, either ccaron or c+combining caron (or l+combining tilde) should
> behave the same way:

  Yes, of course.  This is Unicode canonical equivalence, explained in
the links Idris gave in the Unicode Standard (chapter 2 is "Introduction",
chapter 3 is "Conformance", and we may be concerned by chapter
"Implementation guidelines", too).

> Also, {\v x} and other strange combinations don't work in ConTeXt (I
> guess it does in plain TeX) since ConTeXt MK II uses a clever way to
> figure out if such characters exist in the font encoding

  Mapping sequences like "\v c" to the appropriate slot in the current
font encoding is quite legitimate; LaTeX does the same with its own font
encodings.  I didn't know it meant things like "\v x" couldn't be
displayed, though.  That said, it is something different from supporting
combining characters.

	Arthur
___________________________________________________________________________________
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-01-14  0:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 18:29 Idris Samawi Hamid
2008-01-13  3:31 ` Arthur Reutenauer
2008-01-13 11:18   ` Taco Hoekwater
2008-01-13 14:38     ` Mojca Miklavec
2008-01-14  0:20       ` Arthur Reutenauer [this message]
2008-01-13 18:51     ` Arthur Reutenauer
2008-01-13 22:59   ` Hans Hagen
2008-01-13 23:25     ` Idris Samawi Hamid
2008-01-13 23:30     ` Arthur Reutenauer
2008-01-14  8:59       ` 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=20080114002040.GI5056@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --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).