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: Opening quotes problem with context.
Date: Sat, 27 Jul 2013 17:09:56 +0200	[thread overview]
Message-ID: <CALBOmsbSzm+00o6R0bE+a8zEOX67mH2=VJr+nJfj-D0X62hhhQ@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsaupgUyy8eDJLZOpwrzbC3egbDFvNv_m8-Tdu1NxKWXEA@mail.gmail.com>

On Sat, Jul 27, 2013 at 4:47 PM, Mojca Miklavec wrote:
>
>> I note that the plain TeX version of closing quotes, '' still works.
>
> It doesn't. You get two apostrophes (which usually happen to look like
> a double quotation mark).

I need to add that converting character 27 (') into apostrophe was
considered a crucial functionality, so it was kept. Nobody can imagine
getting the proper apostrophe on keyboard and its use is very common.

On the other hand many languages use different quotation marks and
using ``these'' is completely "americanocentric". On top,
auto-replacement lead to inability to typeset the actual backtick (`)
when it's needed. So yes, getting rid of `` replaced by quotation by
default *was* an improvement.

If you are worried about the number of strokes you can always
configure your keyboard to give the quotation marks by pressing
alt-gr+something (an equivalent effort of typing an uppercase letter).
Or you can define
    \def\q#1{\quotation{#1}}
The big advantage of \quotation{...} is that it automatically gives
you the right quotation marks for the active language. And for me it's
also convenient that I can easily switch which quotation marks are
used (both guilemets and "double comma-style" are allowed in our
grammar, and I sometimes change my mind about which ones should be
used in the middle of the project). Or I could change the quoted text
to become italic.

Mojca

PS: I'm sometimes mad at what TeX did. Every (La)TeX user read a
(La)TeX tutorial at some point and nowadays probably 80% users in my
country still use "\v{c}" (not being aware that they could type the
Unicode characters the same way as they do in Word), either the wrong
font encoding (OT1; without proper hyphenation and with weirdly
composed glyphs) or the bitmap fonts, and the grammatically incorrect
version of ``quotes''. This is what they learnt from manuals. In
ConTeXt UTF-8 just works and \quotation{...} is a lot better than
those weird ``artefacts''.
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2013-07-27 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 15:40 john Culleton
2013-07-22 15:44 ` Wolfgang Schuster
2013-07-23 16:10   ` Sietse Brouwer
2013-07-24 14:58 ` David Rogers
2013-07-24 16:13   ` Wolfgang Schuster
2013-07-27 14:29     ` john Culleton
2013-07-27 14:45       ` Wolfgang Schuster
2013-07-27 14:47       ` Mojca Miklavec
2013-07-27 15:09         ` Mojca Miklavec [this message]
2013-07-27 14:53       ` Marco Patzer

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='CALBOmsbSzm+00o6R0bE+a8zEOX67mH2=VJr+nJfj-D0X62hhhQ@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).