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: using `` '' the output is wrong.
Date: Tue, 19 Jan 2010 20:31:22 +0100	[thread overview]
Message-ID: <6faad9f01001191131l7a924bf6wf98998c6c13af0a8@mail.gmail.com> (raw)
In-Reply-To: <201001181415.56845.alan.braslau@cea.fr>

Let me be a bit more "nationalistic" and exaggerate a bit for a moment
(just in order to explain why I find the idea of using `` a bad one;
do not take the text below too seriously or personally):

On Mon, Jan 18, 2010 at 14:15, Alan BRASLAU wrote:
> On Monday 18 January 2010 13:50:25 Taco Hoekwater wrote:
>> views63 wrote:
>> >
>> > I'm using `` complex analysis'' the output is wrong.
>>
>> Not really. We (Hans and I) would say that it is now finally right. ;)
>
> 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.

- I agree. 80% of Slovenian (La)TeX users use US quotation marks just
because they have read some TeX tutorial about how to use `` and ''.
- Knuth only thought of English quotation marks when implementing the
ugly trick. There is no simple way for "opening quotation marks" („)
for Slovenian/German and most probably for quite some other languages
as well. So ``'' notation is useless for a big fraction of users
anyway. (The only alternative is probably \glqq & friends. You can use
a similar one in ConTeXt as well, but I tend to forget exact names.)
- On Slovenian keyboard it's pretty complicated to type `. Let's take
Mac (but it's equally complicated on Windows). One needs to press
Alt+<+space. This means 2x3=6 strokes to get the character “ typeset.
The character “ itself only takes a single stroke on Mac/Slo. On
Mac/US Int. it's just Alt+[ (2 keystrokes) to get it, so not that bad
either.
- When using \quotation{} it's easy to change the mind about what
quotation marks to use (Slovenian/German use two different sets) and
the proper layout will be used based on the language being used (comes
handy when mixing languages inside the document). Which is great - no
need to think which one to use.
- The deciding moment when some of these ugly tricks have been thrown
away was when we realized that if you do add those tricks, there is no
way to print the grave accent. (Grave accent will be automatically
converted to the same "comma" that you get in quotation marks.) In
good old TeX the grave accent (`) and the character that you get when
you type ` are at two different slots. In Unicode-encoded fonts that's
not doable. This means that if one wants to enable the `` trick then
there's no way to allow composite characters with grave accent or the
character ` in typewriter font. In most cases that is not a problem
since Unicode fonts usually support a wide range of characters, but I
already had to use a character not present in Unicode. And that was
not doable until the hack has been removed.

In the good old days the ugly tricks have been there mostly in order
to compensate for lack of Unicode & accents on keyboards. Nowadays the
limitation of encodings has (almost) gone.

You can easily change the behaviour of ConTeXt by modifying font
features if you insist in using ``''.

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

That's why I always use \quotation{}.

> (Things are even worse on a Mac, as the standard keyboard
> layout is missing lots of important characters.)

I have no idea which keyboard you use, but US International is pretty
rich (the problem is lack of some legend on keyboard itself), on the
other hand it's easy enough to make your own layout.

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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2010-01-19 19:31 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
2010-01-19 19:31     ` Mojca Miklavec [this message]
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=6faad9f01001191131l7a924bf6wf98998c6c13af0a8@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).