ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: TeX ligatures in XeTeX/LuaTeX: ``who needs them''?
Date: Sun, 9 Dec 2007 00:10:34 +0100	[thread overview]
Message-ID: <6faad9f00712081510v1b946b3ax387f4b7f9aa9e6e0@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.9999.0712081721230.5700@nqv-yncgbc>

Hello Aditya,

thanks a lot for your opinion :)

On Dec 8, 2007 11:26 PM, Aditya Mahajan wrote:
> On Sat, 8 Dec 2007, Mojca Miklavec wrote:
>
> 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.

To be honest: I never had the slightest idea how to get proper
(Slovenian, "lower nine double quote") quotation marks in LaTeX (or
what's the suggested way to do it :). That's why I now use
\def\quotation#1{...} in LaTeX as well (in case I need to fix other
people's stuff).

> > 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.
>
> >  ' -> 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.

Sure. Those three replacements/ligatures were not under a question.
They should stay, IMO.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2007-12-08 23:10 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 [this message]
2007-12-09 14:45     ` Henning Hraban Ramm
2007-12-08 23:11   ` Wolfgang Schuster
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=6faad9f00712081510v1b946b3ax387f4b7f9aa9e6e0@mail.gmail.com \
    --to=mojca.miklavec.lists@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).