ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik <rik@panix.com>
To: ntg-context@ntg.nl
Subject: Re: Oddity: \buildtextaccent shifts glyph right
Date: Sun, 6 Sep 2015 12:48:45 -0400	[thread overview]
Message-ID: <55EC6E6D.40908@panix.com> (raw)
In-Reply-To: <55EC6154.3040306@gmx.es>

On 2015-09-06 11:52, Pablo Rodriguez wrote:
> 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

On 2015-09-06 12:20, Thomas A. Schmitz wrote:
> \buildtextaccent has to take some heuristics about horizontal and 
> vertical placement and is sometimes wrong about it. Since your case is 
> somewhat special, I would define a macro for the que symbol and adjust 
> the boxes manually - but then, you'll have to adapt it to italic and 
> upright (and bold) and different font sizes. Depends on how important 
> typographical beauty is to you - either a medium-quality solution for 
> all cases or better quality and manual fiddling... Something like
>
> \definefontfamily [test] [serif] [ebgaramond]
>
> \setupbodyfont [test,12pt]
>
> \define\que%
>   {\bgroup
>    \setbox0\hbox{q}%
>    \setbox2\hbox to \wd0{\kern0.3em\switchtobodyfont[6pt] ʒ}%
>    \setbox4\hbox to \wd0{\kern0.1em\textacute}%
>    \hbox to \wd0 \bgroup
>      \hss\copy0\hss
>      \hskip-\wd0
>      \raise-0.45ex\copy2
>      \hskip-\wd0
>      \raise0.1ex\copy4
>     \egroup
>   \egroup\autoinsertnextspace}
>
> \starttext
>
> {\it Dicit\que mihi}
>
> \stoptext
>
> (btw, the example you sent uses Latin Modern).
>
> Thomas
>



Indeed, for the cases where there are combining accents that is a much 
better solution. I should have chosen a better example, that is, one 
that does not have a combining accent. Fortunately, there are very few 
that fall into that category, and unfortunately, there are some.

Using this, together with Thomas’s code, I can get around these issues.

Thank you both.

(And yes, I had attached the wrong example, and then referred to the 
font therein by the wrong name.)

-- 
Rik
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2015-09-06 16:48 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
2015-09-06 16:48   ` Rik [this message]
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=55EC6E6D.40908@panix.com \
    --to=rik@panix.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).