From: Christian Prim <christian.prim@gmx.ch>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with long indices in LMTX
Date: Mon, 30 Mar 2020 10:43:44 +0200 [thread overview]
Message-ID: <CA+9XOxr04UB2LSmr94+CXx=xzYi7sJDwXZ7dix1GBb2XZmu5Ng@mail.gmail.com> (raw)
In-Reply-To: <CA+9XOxqmqbKA_pfGHmtP3m739=cMBQetsN0jH0Nck7pbJ15oUg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
Hello
For reference: Here is the ConTeXt way of entering a long text-Index, which
works with lmtx:
\starttext
\m{F_{\text{long Index}}=m_{\text{long Index}}a}
\stoptext
Sorry for the noise. (Perhaps a change correlated to the prime
discussion...)
Christian
Am Mi., 25. März 2020 um 09:53 Uhr schrieb Christian Prim <
christian.prim@gmx.ch>:
> Hello list
>
> Sorry to ask again. What do I miss in following MWE?
>
> \starttext
> \m{F_{\rm longIndex}=m_{\rm longIndex}a}
> \stoptext
>
> The index longIndex overlaps the following characters "=" and "a" when
> processed with lmtx. No problems with mkiv.
>
> Thanks for your help
> Christian
>
> Am Sa., 21. März 2020 um 17:27 Uhr schrieb Christian Prim <
> christian.prim@gmx.ch>:
>
>> Hello
>>
>> Following MWE produces strange output in latest LMTX. mkiv (also latest)
>> output is ok.
>>
>> \usetypescript[palatino]
>> \setupbodyfont[palatino,11pt]
>> \starttext
>> \m{F_{\rm longIndex}=m_{\rm longIndex}a}
>> \stoptext
>>
>> The spacing in the index is wrong.
>>
>> What am I missing?
>>
>> Thanks in advance
>> Christian
>>
>
[-- Attachment #1.2: Type: text/html, Size: 1984 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-03-30 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 16:27 Christian Prim
2020-03-25 8:53 ` Christian Prim
2020-03-30 8:43 ` Christian Prim [this message]
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='CA+9XOxr04UB2LSmr94+CXx=xzYi7sJDwXZ7dix1GBb2XZmu5Ng@mail.gmail.com' \
--to=christian.prim@gmx.ch \
--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).