ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Underbar offset
Date: Thu, 26 May 2016 18:17:30 +0200	[thread overview]
Message-ID: <83a71c52-1b67-a11a-1810-d90f7543c7a2@wxs.nl> (raw)
In-Reply-To: <CALBOmsZMEVY4QEbVfe18z+igm0_+yNwq6QwEB0UaR0sp2To1UQ@mail.gmail.com>

On 5/26/2016 2:48 PM, Mojca Miklavec wrote:
> On 25 May 2016 at 17:35, Wolfgang Schuster wrote:
>>
>> With \shiftup the line under the raised text stays at the same position.
>>
>> \starttext
>> \underbar{Test this \shiftup{®}}
>> \stoptext
>
> When has \shiftup been implemented?
>
> It doesn't work in TeX Live (or maybe I forgot to update TL to the
> latest version), but works with the latest version of ConTeXt.

it has always been there but recently i saw that when i had updated some 
low level stuff (to new luatex) i had forgotten something, so i fixed that

> Nevertheless this doesn't entirely solve the problem. I now have a
> problem with the following:
>
>     \catcode`č=\active
>     \defč{\buildtextaccent\textcaron c}

doesn't the compose=yes feature work?

>     \underbar{Test this č}
>
> I will try to remember how to fix the font on the fly with lua (or
> perhaps figure out how to edit the font; it's a commercial font
> though, so fixing it "on the fly" would probably be better).
>
> I will also test some other piece of code that Hans sent me off-list.
> (I seem to remember that there must be some tens of ways to underline
> text. Every now and then Hans sends a new demo.)

so let's give you another piece

\startluacode
fonts.handlers.otf.addfeature {
     name = "mojca",
     type = "multiple",
     prepend = true,
     data = {
         ["č"] = { 0x30C, "c" },
     }
}
fonts.handlers.otf.addfeature {
     name = "kern",
     type = "pair",
     data = {
         [0x30C] = { c = { { 500, 0, 0, 0 }, false } },
     }
}
\stopluacode

\definefontfeature[default][default][mojca=yes]

\showframe

\starttext

     mojča miklave\utfchar{"30C}c

\stoptext

(actually it uncovered a buglet but i suppose the č never is the first 
char so ...)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2016-05-26 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 23:54 Mojca Miklavec
2016-05-24 12:19 ` Hans Hagen
2016-05-25 15:35   ` Wolfgang Schuster
2016-05-26 12:48     ` Mojca Miklavec
2016-05-26 13:10       ` Marco Patzer
2016-05-26 15:20       ` Aditya Mahajan
2016-05-26 16:17       ` Hans Hagen [this message]
2016-05-26 17:24         ` Mojca Miklavec

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=83a71c52-1b67-a11a-1810-d90f7543c7a2@wxs.nl \
    --to=pragma@wxs.nl \
    --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).