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: lost curved left quotes
Date: Tue, 4 Aug 2009 19:29:03 +0200	[thread overview]
Message-ID: <6faad9f00908041029g2f1e5689s6e0a6adb1dea8e2@mail.gmail.com> (raw)
In-Reply-To: <33c64e670908040947o1d56cce9h83ee0e425e852893@mail.gmail.com>

On Tue, Aug 4, 2009 at 18:47, Derek CORDEIRO wrote:
> On Tue, Aug 4, 2009 at 8:57 PM, Ciro Soto wrote:
>>
>> I am resending this just in case it got lost when the server was down.
>>
>>
>>
>>
>> Hi all,
>> Somehow my left quotes are straight, not curved as my right quotes.
>> How could I make them curved?
>> (I am using `` for the left quotes, and '' for the right quotes.)
>> (If I use \quotation {qwerty}  I get the curved quotes in both sides)
>
> I think thats the way Mk IV is supposed to be, you could type the “double
> quotes” in from your keyboard.

> Using texexec(Mk II) you should get the old
> behavior, i.e. `` = “

True, but one should nevertheless better use \quotation{...} or
“double quotes” both in MKII and MKIV. The MKII behaviour is a hack
that works with Latin Modern (as it did in Computer Modern). The
reason why it works is that there are hacky ligatures in that font. If
you were using any other font, you would not get the "curly" quotes
(but you probably wouldn't dare generating tfm files yourself, so you
would never notice that). People that do generate tfm files make sure
to artificially add those ligatures.

MKIV has deliberately chosen no to support that hackery ***. There are
three exceptions though:
- endash (--) and emdash (---)
- apostrophe (')
since we all agreed that those are still hard enough to type or at
least hard enough to distinguish (esp. the dashes in monospace font)
even if they do have their own Unicode codepoint.

Mojca

*** partially also because of another ugly overlap or coincidence;
namely -- grave accent and ` share the same codepoint in Unicode, so
it would be impossible to support both placing grave accent and
automatic "conversion" of ` into curly quotes at the same time; TeX
fonts use two different characters for that)
___________________________________________________________________________________
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:[~2009-08-04 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <297ee2eb0907271641m51afc40ahd5ceba49c3480fd@mail.gmail.com>
2009-08-04 15:27 ` Ciro Soto
2009-08-04 16:47   ` Derek CORDEIRO
2009-08-04 17:29     ` Mojca Miklavec [this message]

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=6faad9f00908041029g2f1e5689s6e0a6adb1dea8e2@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).