From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: TeX ligatures in XeTeX/LuaTeX: ``who needs them''?
Date: Sun, 9 Dec 2007 00:11:03 +0100 [thread overview]
Message-ID: <20071209001103.c134a089.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.0.9999.0712081721230.5700@nqv-yncgbc>
On Sat, 8 Dec 2007 17:26:48 -0500 (EST)
Aditya Mahajan <adityam@umich.edu> wrote:
> On Sat, 8 Dec 2007, Mojca Miklavec wrote:
>
> > just wondering: how many ConTeXt-ers depend on ligatures such as:
> > '' (double quote) and '' (two single quotes) -> right double quote
> > `` -> left double quote
>
> In some old documents. In newer documents I use \quote and \quotation.
> Then there are documents that need to move back and forth between latex
> and context but for them I can easily define appropriate macros in latex.
>
> > ,, -> DOUBLE LOW-9 QUOTATION MARK
We should jeep them for old times sake although I prefer quote and
quotation in my document because this is more flexible (change with the
language and I can also change the quotation style).
> > or even more weird ones:
> > !` -> inverted exclam
> > ?` -> inverted question
> > << -> LEFT POINTING GUILLEMET (never heard of that ligature)
> > >> -> RIGHT POINTING GUILLEMET
>
> I have never used them.
The two spain ligatures should vanish, I tried once to write [...]?`` in
one of my documents and hated this behaviour. The other two ligatures
for guillemets another odd things because I < in my document for every
< in my source not a replacement.
> > Some ligatures are handy indeed:
> > -- -> endash
> > --- -> emdash
>
> I use them all the time. Even though the utf encoded values can work here,
> my editor (vim) using fixed width fonts, so it is easy to miss the
> difference between hypehn, endash, and emdash (in the markup). So, I would
> prefer them to be present.
Keep them, they are to usefull. I could also agree to Aditya's
explanation.
> > ' -> right single quote (I'm, isn't etc.)
>
> I can automate the conversion of ' to the corresponding utf character
> inside vim, so this is not really essential. However, IMO this should not
> change.
>
> Aditya
I nearly never need this in my documents but it is very usefull in I
don't want to select the right character. This is also on of the points
Word and Powerpoint users select the wrong character but TeX has
always the right character :-)
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-08 23:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 22:04 Mojca Miklavec
2007-12-08 22:26 ` Aditya Mahajan
2007-12-08 23:10 ` Mojca Miklavec
2007-12-09 14:45 ` Henning Hraban Ramm
2007-12-08 23:11 ` Wolfgang Schuster [this message]
2007-12-09 16:07 ` Willi Egger
2007-12-09 18:48 ` Mojca Miklavec
2007-12-10 8:46 ` Wolfgang Schuster
2007-12-10 8:49 ` Willi Egger
2007-12-10 5:55 ` Maurício
2007-12-10 8:41 ` Hans Hagen
2007-12-10 12:24 ` Maurício
2007-12-10 12:38 ` 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=20071209001103.c134a089.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.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).