From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Oddity: \buildtextaccent shifts glyph right
Date: Sun, 6 Sep 2015 17:52:52 +0200 [thread overview]
Message-ID: <55EC6154.3040306@gmx.es> (raw)
In-Reply-To: <55EC5B7A.6060103@panix.com>
On 09/06/2015 05:27 PM, Rik wrote:
> I am using \buildtextaccent to create a couple of characters that have
> no Unicode equivalent.
Hi Rik,
although they don’t seem to work as expected in ConTeXt, Unicode has
combining diacritical marks (as you might know), such as:
U+0301 COMBINING ACUTE ACCENT
Just in case it might help,
Pablo
They are scribal abbreviations that made it into
> early typesetters works. In this case, the abbreviation are for Latin
> que, which looks like a q with a small ezh appended in a subscript
> position, and q with an acute accent, both of which are used in some
> 17th century works I am dealing with. An example of the abbreviation
> with the ezh and accent can be seen at
> https://books.google.com/books?id=hHNVAAAAcAAJ&pg=PA6#v=onepage&q&f=false in
> the sixth line of the paragraph beginning “Yea but”.
>
> It seems that \buildtextaccent\textacute q (or \buildtextaccent´q) moves
> the q to the right within the character’s bounding box. The following
> example (and attached resulting pdf) demonstrates this. Lines 1 and 2
> show the string with and without the \buildtextaccent, and lines 4 and 6
> repeat that in italic. The strings are the same width, but the q is
> moved right. Lines 3 and 6 show a manual kerning of the q to improve
> appearance.
>
> This happens with many fonts, but not all (I do not see it with Computer
> Modern). I am using Win 10Pro x64 with ConTeXt ver: 2015.09.04 11:00
> MKIV beta fmt: 2015.9.5 int: english/english.
>
> I suspect that this is not intended, but I am not sure.
>
> I would also love to raise the accent a bit. Suggestions? I can live
> with it as it is and manually kern as needed. There are very few
> instances of these abbreviations that need to be dealt with.
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2015-09-06 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 15:27 Rik
2015-09-06 15:52 ` Pablo Rodriguez [this message]
2015-09-06 16:48 ` Rik
2015-09-06 16:20 ` Thomas A. Schmitz
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=55EC6154.3040306@gmx.es \
--to=oinos@gmx.es \
--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).