From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: incosistent output of --- dash
Date: Sat, 6 Apr 2024 12:23:55 +0200 [thread overview]
Message-ID: <5f123f99-3d45-43d5-bde6-5cf814ac7d15@fiee.net> (raw)
In-Reply-To: <171239660291.3369327.17842960041450679863@cgl.ntg.nl>
Am 06.04.24 um 11:43 schrieb madiazm.eoicc@gmail.com:
> Hi everyone,
> I'm a bit puzzled because I usually don't get an em-dash when I type tree hyphens. If I use the command \emdash, no problem but when I use the hyphens some days it works... and somedays I see three small hyphens.
> I tried it on overleaf and of ContextOnWeb with the same inconsistency. If I create a new file it usually works right; but when I overwrite an existing file subtituting a hyphen for three where the dash should be I sometimes get it right and sometimes wrong.
> It is not the pdf viewer since I get good or bad results in all, the overleaf pdf preview tool, the context on web preview tool and the mozilla integrated pdf viewer.
>
> Am I missing something on the use of this ligature? (the question is just out of curiosity, since I plan to create a command that adds a hairspace after or before the dash, since I don't like it to stick to some letters like "o".
Generally, “we” try to reduce active characters as much as possible,
that’s why -- and --- usually /don’t/ produce en or em dashes. You can
activate these ligatures as a font feature though (AFAIR "latexhyphens",
can’t find it…).
Some editors and some fonts do automatical replacements.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-04-06 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 9:43 [NTG-context] " madiazm.eoicc
2024-04-06 10:23 ` Henning Hraban Ramm [this message]
2024-04-06 11:38 ` [NTG-context] " Wolfgang Schuster
2024-04-07 5:41 ` Hans Hagen
2024-04-07 6:04 ` vm via ntg-context
2024-04-06 11:08 ` Pablo Rodriguez via ntg-context
2024-04-07 17:56 ` madiazm.eoicc
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=5f123f99-3d45-43d5-bde6-5cf814ac7d15@fiee.net \
--to=texml@fiee.net \
--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).