ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: ntg-context@ntg.nl
Subject: Re: using `` '' the output is wrong.
Date: Mon, 18 Jan 2010 14:15:56 +0100	[thread overview]
Message-ID: <201001181415.56845.alan.braslau@cea.fr> (raw)
In-Reply-To: <4B545911.1050400@elvenkind.com>

On Monday 18 January 2010 13:50:25 Taco Hoekwater wrote:
> Hi,
> 
> views63 wrote:
> > Hi  all,
> >
> > I'm using `` complex analysis'' the output is wrong.
> 
> Not really. We (Hans and I) would say that it is now finally right. ;)
> 
> > but using \ quotation (... ...) can output the correct quotation marks
> 
> This is the right way to do it. Alternatively, you can use unicode
> characters to input the correct quotation marks.
> 
> Best wishes,
> Taco

This is true of many standard TeX ligatures (is this the right word here?)
such as ... (\ldots, \dots also works), << (\og), >> (\fg), "` (\glqq),
"' (\grqq), ~ (unbreakable space), etc.

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.
(Things are even worse on a Mac, as the standard keyboard
layout is missing lots of important characters.)

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


  parent reply	other threads:[~2010-01-18 13:15 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 [this message]
2010-01-18 13:47     ` Henning Hraban Ramm
2010-01-18 13:53     ` Hans Hagen
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=201001181415.56845.alan.braslau@cea.fr \
    --to=alan.braslau@cea.fr \
    --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).