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: Wed, 20 Jan 2010 08:28:47 +0100	[thread overview]
Message-ID: <201001200828.47505.alan.braslau@cea.fr> (raw)
In-Reply-To: <4B56AB0B.5040100@elvenkind.com>

On Wednesday 20 January 2010 08:04:43 Taco Hoekwater wrote:
> The problem is that all the latex and plain tex books promote
> the use of `` and '' and people that already use TeX are unlikely
> to change their habits (and most will not read the context manual
> as thoroughly as they should).
> 

This is my concern. Whereas I do prefer \quotation{} being functionally 
logical, after all the spirit of TeX, I also like unicode generalizations 
(such as ± for \pm). Nevertheless, hard core TeX users as well as converts 
from LaTeX *expect* ``'', --, ---, ..., etc. to work in ConTeXt. I assume that 
the present discussion is useful and not simply controversial.

I ignore the mechanisms behind the different implementations (macro, fonts, 
catcar, ...) and the problems that arise.

Concerning typesetting source code, I would suggest something as simple as 
suspending ALL such tricks within \text{} and \starttyping\stoptyping (perhaps 
parametrized). One could also define something like \shellescape{}, analogous 
to \quotation{}, to typeset `echo "hello world"` and even \string{} to typeset 
"string" or 'string', according to the programming language initialized.

What I also find disturbing is that *some* of these conventions are retained, 
but not all.

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
___________________________________________________________________________________


  reply	other threads:[~2010-01-20  7:28 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
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 [this message]
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=201001200828.47505.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).