From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: composing characters in MKIV
Date: Thu, 30 Sep 2010 23:14:08 +0200 [thread overview]
Message-ID: <AANLkTikSHOOKzXD-juWf8An-+rkt2Ok_ZZE8H5ZPFwHc@mail.gmail.com> (raw)
In-Reply-To: <4CA4EFB7.4070307@wxs.nl>
On Thu, Sep 30, 2010 at 22:14, Hans Hagen wrote:
>
> \starttext
>
> \definefontfeature[default][default][compose=yes]
>
> \setupbodyfont[lucida]
Oh, I have tried that; actually I did
\definefontfeature[default][liga=yes,kern=yes,tlig=yes,compose=yes]
as well as \addff{compose}, but it had zero effect since I used that
*after* \setupbodyfont instead of using it before. This was a bit
weird since features for OpenType fonts can be switched on and off at
any given time and I didn't realize that order was important.
> \startTEXpage
> mojča MOJČA
> \stopTEXpage
>
> \stoptext
>
> ok, positioning could be improved I guess but so far no one bothered about
> this feature
(I started fixing vf fonts of Lucida for pdfTeX, but I'm not sure how
to proceed; and now it may not be needed any more.)
There are two problems. Even \buildtextaccent creates an ugly č and
that dates back to Knuth's TeX (TeX assumes that every letter is
symetric which holds for just about any letter but c). But I agree
that this is highly esoteric request.
However compose=yes creates an unacceptable uppercase Č, at least in
Lucida, much worse than what TeX does (and already TeX does it badly).
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-09-30 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 18:31 Mojca Miklavec
2010-09-30 20:14 ` Hans Hagen
2010-09-30 21:14 ` Mojca Miklavec [this message]
2010-09-30 21:21 ` 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=AANLkTikSHOOKzXD-juWf8An-+rkt2Ok_ZZE8H5ZPFwHc@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).