ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Need for \buildtextaccent, was Re: latest beta
Date: Fri, 17 Jan 2014 19:39:29 +0100	[thread overview]
Message-ID: <CALBOmsZsh6V--qnWqvv9d7p=w=05jADJ1aM3BhH5e=q6c8EaYg@mail.gmail.com> (raw)
In-Reply-To: <52D9723A.4080501@wxs.nl>

On Fri, Jan 17, 2014 at 7:11 PM, Hans Hagen wrote:
>
> do we need a module with predefined 'missing from unicode' characters?

I don't think so. We can end up with a neverending and always
incomplete list (with theoretically unlimited number of entries),
usable only to those few people who will care to contribute. In my
opinion such a list is pretty much useless.

Unicode already specifies that one could use "q" followed by
"combining acute". And TeX also has support for {\'q}. Everything else
is private use, something that users might not even use in more than a
single document. I don't see any advantage in creating an endless
incomplete list. In all honesty it's a lot more
useful/readable/straightforward to use {\'q} or proper Unicode in
these cases. And if it's not comfortable enough for the user, he can
always provide his own private definitions.

Thomas and Rik most probably need just the existing mechanism to work
properly. Well, it might be slightly different for Thomas where
Ancient Greek has a limited set of letters, but then such a list
should better be defined in an "ancient greek predefined characters
module".

Just my 2 cents.

Mojca
___________________________________________________________________________________
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:[~2014-01-17 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 22:23 Thomas A. Schmitz
2014-01-17 11:22 ` Hans Hagen
2014-01-17 16:04   ` Need for \buildtextaccent, was " Rik Kabel
2014-01-17 18:11     ` Hans Hagen
2014-01-17 18:39       ` Mojca Miklavec [this message]
2014-01-17 18:51         ` Hans Hagen
2014-01-17 20:23         ` Thomas A. Schmitz
2014-01-17 20:45         ` Arthur Reutenauer

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='CALBOmsZsh6V--qnWqvv9d7p=w=05jADJ1aM3BhH5e=q6c8EaYg@mail.gmail.com' \
    --to=mojca.miklavec.lists@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).