From: Art Chimes <artsonline@gmail.com>
To: ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Old-Style numerals command (\os) breaks conversion of hyphens to dashes
Date: Sun, 20 Sep 2020 17:14:52 -0400 [thread overview]
Message-ID: <CAM1EaW79zy6EnsijcHQh_EPkFqdmUB9Qz1tzZ=NROqYbjHGZVQ@mail.gmail.com> (raw)
I have a fairly large document, 50-60 pp, with lots of numerals,
including hundreds of dates. I wanted to see how it would look with
old-style numbers and I assumed I could bracket the whole text section
of the document within braces and apply the \os command. I didn't turn
out as I expected, however. It did convert the numbers to old-style
digits. But it also unexpectedly changed the em and en dashes back to
hyphens, as they were entered in the source .tex document.
MWE follows below.
I could possibly do a search-and-replace but I am hoping there is a
simpler way to do it.. I am using Libertinus Serif (which does support
old style numerals) and columns, if that matters. Thank you.
\starttext
First two examples: Brackets surround text including digits, grouped
hyphens are {\emph not} converted to en and em dashes.
{\os
Ford--Chevy 12345
Chrysler---Plymouth 67890
}
\blank[line]
Next two examples: Brackets surround just the digits, the grouped
hypehns {\emph are} correctly converted to en and em dashes
Honda--Toyota {\os 12345}
Renault---Volkswagen {\os 67890}
\stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2020-09-20 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 21:14 Art Chimes [this message]
2020-09-21 6:35 ` 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='CAM1EaW79zy6EnsijcHQh_EPkFqdmUB9Qz1tzZ=NROqYbjHGZVQ@mail.gmail.com' \
--to=artsonline@gmail.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).