ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: composing commands
Date: Fri, 5 Feb 2021 23:29:32 +0100	[thread overview]
Message-ID: <d5f8b6c2-682b-1dad-e796-1b251b3bcdd0@xs4all.nl> (raw)
In-Reply-To: <725a4491-daaa-df10-2b3c-d784c232701d@uni-bonn.de>

On 2/5/2021 6:19 PM, Thomas A. Schmitz wrote:
> 
> On 2/5/21 5:38 PM, Hans Hagen wrote:
>> etc ... the ones that make 'composed characters'. I think that anyone 
>> who needs them uses utf . They can be in (say) m-oldschool.mkxl or so.
>>
>> Objections? Hurt feelings? Sentiments?
> 
> No hurt feelings, but I know that in my bib files, there are a couple of 
> old entries that still have these weird composed characters. So I'm fine 
> with upgrading, but it would be nice if this could fail gracefully, with 
> a nice and informative error message...
btw, something like that will never happen suddenly ... more a matter of 
declaring them obsolete, maybe move them so a module that we could still 
load by default and later maybe on demand

concerning bibtex files, that's another story ... in order to deal well 
with sorting etc quite a bit of sanitizing already takes place there 
(alan and i spent quite a bit of time on that); also there are ways to 
define extra only-used-in-bibtex commands, so we could actually just 
define them for bib stuff only

it's more about "what are the current habits" ... we have commands like 
\" (which is kind of intuitive) but \r and \v and such fall in the 
category, and there are more kind of accents than we currently have 
commands for anyway

a similar discussion (and we already exchanged some mails about that) 
are named glyphs ... we have quite some for latin, greek, cyrillic (like 
\eacute) but how about the rest of unicode

makes me wonder if we should have

   \chr{e"a'}

producing

   ëá

(using real combinings is ok already) which is trivial to implement so 
for the fun of it i might as well add that; i think most who deal with 
languages that have characters other than ascii will input in the most 
natural way so we're only talking of escapes for those who see accents 
and such as noise (yes we do have accents in dutch)

(in mkii we already had utf so then we actually did much of the 
transition but mkii is stone age in terms of software)

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
___________________________________________________________________________________

  parent reply	other threads:[~2021-02-05 22:29 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 [this message]
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
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=d5f8b6c2-682b-1dad-e796-1b251b3bcdd0@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).