From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: using `` '' the output is wrong.
Date: Mon, 18 Jan 2010 14:53:01 +0100 [thread overview]
Message-ID: <4B5467BD.2020006@wxs.nl> (raw)
In-Reply-To: <201001181415.56845.alan.braslau@cea.fr>
On 18-1-2010 14:15, Alan BRASLAU wrote:
> This is true of many standard TeX ligatures (is this the right word here?)
actually they are inoput tricks misusing tex's ligature mechanism and
there are also some weird ones (never used in practice)
> such as ... (\ldots, \dots also works),<< (\og),>> (\fg), "` (\glqq),
> "' (\grqq), ~ (unbreakable space), etc.
~ is a macro
> This can be a bit disturbing for experienced TeX users.
>
> OK, \quotation{} is cleaner and of course using unicode
> characters may be even more readable, sometimes.
>
> I have very mixed feelings, as I know how to type ...
> but I never can recall the keyboard gymnastics necessary
> to get this in unicode.
\somenameforasymbol is always okay
but as taco mentioned ... in mkiv these pseudo ligs are sort of gone
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-01-18 13:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 12:34 views63
2010-01-18 12:50 ` Taco Hoekwater
2010-01-18 13:11 ` views63
2010-01-18 13:15 ` Alan BRASLAU
2010-01-18 13:47 ` Henning Hraban Ramm
2010-01-18 13:53 ` Hans Hagen [this message]
2010-01-19 19:31 ` Mojca Miklavec
2010-01-19 20:04 ` Aditya Mahajan
2010-01-19 20:10 ` Alan BRASLAU
2010-01-19 20:23 ` Wolfgang Schuster
2010-01-19 20:26 ` Aditya Mahajan
2010-01-19 20:34 ` Wolfgang Schuster
2010-01-19 20:44 ` Aditya Mahajan
2010-02-03 13:56 ` Wolfgang Schuster
2010-01-19 20:28 ` Aditya Mahajan
2010-01-19 21:01 ` Hans Hagen
2010-01-19 21:02 ` Mojca Miklavec
2010-01-20 7:04 ` Taco Hoekwater
2010-01-20 7:28 ` Alan BRASLAU
2010-01-20 7:52 ` Peter Münster
2010-01-20 9:10 ` Hans Hagen
2010-01-20 9:58 ` Alan BRASLAU
2010-01-20 10:39 ` Taco Hoekwater
2010-01-20 14:42 ` Mojca Miklavec
2010-03-04 18:41 ` Khaled Hosny
2010-03-04 18:31 ` Khaled Hosny
2010-01-20 9:03 ` Hans Hagen
2010-01-19 22:08 ` Peter Münster
2010-03-04 18:19 ` Khaled Hosny
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=4B5467BD.2020006@wxs.nl \
--to=pragma@wxs.nl \
--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).