ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Re: Horizontal space in math subscript generated by Lua
Date: Wed, 15 Dec 2010 18:11:34 +0100	[thread overview]
Message-ID: <op.vnrl1kyytpjj8f@lpr> (raw)
In-Reply-To: <4D08AF52.4070707@wxs.nl>

Hello,

On Wed, 15 Dec 2010 13:06:42 +0100, Hans Hagen <pragma@wxs.nl> wrote:

> actually, the luacode was doing the right thing as there is a protect/unprotect mismatch (will be fixed); puttingthis at the top of you file works:
>
> \catcodetable\ctxcatcodes

thank you, Hans.

This makes both solutions (Ctx generated and Lua generated) equal - [wider] spacing is the same.

Just my point of view - the previous native Ctx result (= narrower spacing in subscript when mixing upper and lower case letters) - seemed to me a bit prettier; wouldn't be better to keep the "old" Ctx look (= result without \catcodetable\ctxcatcodes) and to drive Lua to give the same result?

Best regards,

Lukas


-- 
Ing. Lukáš Procházka [mailto:LPr@pontex.cz]
Pontex s. r. o.      [mailto:pontex@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 244 062 238
Fax: +420 244 461 038

___________________________________________________________________________________
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:[~2010-12-15 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 11:25 Procházka Lukáš Ing. - Pontex s. r. o.
2010-12-15 12:06 ` Hans Hagen
2010-12-15 17:11   ` Procházka Lukáš Ing. - Pontex s. r. o. [this message]
2010-12-18 21:08     ` 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=op.vnrl1kyytpjj8f@lpr \
    --to=lpr@pontex.cz \
    --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).