ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Opening quotes problem with context.
Date: Wed, 24 Jul 2013 18:13:18 +0200	[thread overview]
Message-ID: <CF413A8A-89C0-45D1-98AF-52586202BFB1@gmail.com> (raw)
In-Reply-To: <87zjtct36a.fsf@gmail.com>


Am 24.07.2013 um 16:58 schrieb David Rogers <davidandrewrogers@gmail.com>:

> john Culleton <John@wexfordpress.com> writes:
> 
>> Did a fresh install of context etc. from the context site. I used this
>> test file:
>> -------------------------------
>> \starttext
>> ``Hello world.'' And ``Goodbye world.''
>> \stoptext
>> %\bye
>> -----------------------------------------
>> The resulting pdf shows two left tick marks for opening quotes but the
>> closing quotes are proper curly quotes.
>> 
>> If I modify the file as follows:
>> -------------------------------
>> %\starttext
>> ``Hello world.'' And ``Goodbye world.''
>> %\stoptext
>> \bye
>> ---------------------------
>> and use luatex or pdftex from texlive the quotes are OK. 
>> 
>> I got similar results from context in texlive 2012 and texlive 2013.
>> 
>> What is the proper code for opening quotes in context?
> 
> 
> The "truly proper" code is \quotation{Hello world.} - that style is
> guaranteed to work. (And, for instance, if you change context's language
> to French, then \quotation{Bonjour monde.} will automatically give you
> the correct style of French quotation marks without having to look up
> how to type them; likewise for other languages.)

There is nothing wrong by using „ “ ” « » etc. for quotations. When you
use \quotation etc. you don’t have to bother about the correct marks
for your language (you can also change them) but the code is easier to
read when you use the real signs.

> I think the problem of the two left tick marks may come from web browser
> copy-and-paste. Special marks, especially the quotation marks,
> apostrophes, and tick marks, are often mangled when converting to and
> from HTML. When copying any program's code from a web page, watch out
> for those marks, they've probably been mis-transcribed by the too-clever
> HTML rendering.

What John wrote is valid in plain TeX where fonts replaced `` and ''
with the proper characters in MkIV this feature was dropped because
you can use \quotation or write the characters in your text.

Wolfgang
___________________________________________________________________________________
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-24 16:13 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 [this message]
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
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=CF413A8A-89C0-45D1-98AF-52586202BFB1@gmail.com \
    --to=schuster.wolfgang@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).