ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Typographical quotes
Date: Sat, 27 Nov 2021 20:15:34 +0100	[thread overview]
Message-ID: <a5e1d514-3f91-c716-cc39-afca0afd88ee@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2111271235360.1710690@nqv-guvaxcnq>

On 11/27/2021 6:40 PM, Aditya Mahajan via ntg-context wrote:
> On Sat, 27 Nov 2021, Wolfgang Schuster via ntg-context wrote:
> 
>> Jean-Philippe Rey via ntg-context schrieb am 27.11.2021 um 16:21:
>>> Dear list,
>>>
>>> When typing a straight quotation mark, I used to get a curly apostrophe. But
>> with a recent version of ConTeXt, I now get a straight apostrophe. Is there a
>> new option to convert automatically straight into curly apostrophes ?
>>>
>>> \starttext
>>> John's
>>> \stoptext
>>
>> The option is no longer part of the default feature set.
> 
> Personally, I think that that is a bit extreme. An apostrophe is a really common construct and I suspect that this change in default will mean that almost everyone needs to add tlig in their documents. We may perhaps need a 'sensible-defaults' module :-)
we entered the unicode world and left ascii space so for instance the 
ugly enter `` '' and expect english double quotes is also a not-done 
now, nor are !` and ?` for the spacing rotated ! and ?; i can't find the 
font right now but there were with interesting space-something ligatures 
that only didn't show up because tex has no space.

anyway, these kind of auto font dependent remappings and ligatures are 
kind of tricky because they depend on the font and as such are a rather 
specific 8 bit tex thing ... also, to some extend

now, there are more tex traditions that context doesn't support; take 
this plain definition (there are many) dedicated to math users:

\mathcode`\^^D="225E % \land

which gives

\starttext
	$^^D$
\stoptext

and as it's plain it's documented and in the tex book so users can 
expect it. It's for those who can afford a 
https://www.artlebedev.com/optimus/maximus/ (i don't have one and it's 
no longer for sale, alas).

Anyway, it's easier to enabel a feature that to disable one when side 
effects of font handling kicks in happen.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-11-27 19:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 15:21 Jean-Philippe Rey via ntg-context
2021-11-27 16:47 ` Denis Maier via ntg-context
2021-11-27 16:47   ` Denis Maier via ntg-context
2021-11-27 16:59 ` Wolfgang Schuster via ntg-context
2021-11-27 17:04   ` Denis Maier via ntg-context
2021-11-27 17:08     ` Wolfgang Schuster via ntg-context
2021-11-27 17:40   ` Aditya Mahajan via ntg-context
2021-11-27 19:15     ` Hans Hagen via ntg-context [this message]
2021-11-27 20:48       ` Aditya Mahajan via ntg-context
2021-11-28 10:32         ` Hans Hagen via ntg-context
2021-11-28 10:44           ` Henning Hraban Ramm via ntg-context
2021-11-28 11:20             ` Hans Hagen via ntg-context
2021-11-27 21:09     ` Henning Hraban Ramm via ntg-context
2021-11-27 18:47   ` Jean-Philippe Rey via ntg-context

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=a5e1d514-3f91-c716-cc39-afca0afd88ee@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).