ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Otared Kavian <otared@gmail.com>
Subject: Re: composing commands
Date: Fri, 5 Feb 2021 23:47:50 +0100	[thread overview]
Message-ID: <e7b4ceb2-72e3-5a8f-962c-fb26ff217cdd@xs4all.nl> (raw)
In-Reply-To: <9A31BF6A-CCD0-4B2F-9B9D-E4742F3218EC@gmail.com>

On 2/5/2021 11:21 PM, Otared Kavian wrote:
> Hi Hans,
> 
> I agree that nowadays most composed characters can be input directly from the keyboard (at least judging from my experience with MacOS), but nevertheless it may happen that one uses an old file used as an input source file (for instance extracting a math exercise from a database) in which there are old fashion composed characters. It would be hard to go back and replace those characters in each file.
> Besides, with the traditional plain TeX composed characters something like
> 
> \"c

indeed, not in unicode ... so unlikely dealt with in fonts (i could of 
course support it as in mkii but in over a decade no one complained so ...)

> would give a correct result (the character c with a kind of umlaut on top of it), but this cannot be input from the keyboard (and maybe it does not exist at all in UTF…). (Actually I just tried \"c with LMTX and mkiv and it does not give what is expected from TeX… I am sure it did work some years ago :-) )

never call a diaeresis an umlaut and vise versa ... some texies can get 
very emotional about that ... and you don't want to know how long 
winding and boring discussions about the distance between the base 
character and the accent can/has/might be (i remember some discussion 
about the umlaut being lower positioned given its historis origin, it 
being tiny letters) ... often discussions focused on computer modern 
because that was kind of under control (we had plenty of variants for 
each language, which is interesting because they actually could be in 
one font, but that (a new encoding as part of texgyre) happened just 
before we all went unicode and before the european union became larger

> If, as you suggest, such composed characters maybe used at the cost of saying at the beginning of one's file:
> 	\usemodule[oldschool]
> then there is no real harm in removing composing commands, although I am not an enthusiastic supporter of removing them.
Well, that why I ask.

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-02-05 22:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 16:38 Hans Hagen
2021-02-05 16:49 ` Jairo A. del Rio
2021-02-05 21:28   ` Hans Hagen
2021-02-05 17:19 ` Thomas A. Schmitz
2021-02-05 21:30   ` Hans Hagen
2021-02-05 22:25     ` Otared Kavian
2021-02-05 22:39       ` Hans Hagen
2021-02-05 23:01     ` Thomas A. Schmitz
2021-02-05 23:49       ` Hans Hagen
2021-02-05 22:29   ` Hans Hagen
2021-02-06 22:41     ` T. Kurt Bond
2021-02-08  9:53       ` Hans Hagen
2021-02-08 21:42         ` Richard Mahoney
2021-02-09 10:03         ` Otared Kavian
2021-02-09 13:08           ` Hans Hagen
2021-10-11 11:06         ` Marcus Vinicius Mesquita via ntg-context
2021-02-07 19:40   ` Hans Hagen
2021-02-05 22:21 ` Otared Kavian
2021-02-05 22:47   ` Hans Hagen [this message]
2021-02-05 23:45     ` luigi scarso

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=e7b4ceb2-72e3-5a8f-962c-fb26ff217cdd@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    /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).