From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Otared Kavian <otared@gmail.com>,
rmahoney@indica-et-buddhica.org
Subject: Re: composing commands
Date: Tue, 9 Feb 2021 14:08:24 +0100 [thread overview]
Message-ID: <1a4b71ef-711f-50dd-0e3e-70e9769391c3@xs4all.nl> (raw)
In-Reply-To: <B4937A7B-47A8-4DBC-AEBB-C0D722D6D6AB@gmail.com>
On 2/9/2021 11:03 AM, Otared Kavian wrote:
> Hi Hans,
>
> Thanks for the new composing commands. I made several tests and everything works great.
> I guess when you say something like
>
>> \withgrave {a} == \\`{a}
>
> you mean
>
> \withgrave {a} == \`{a}
>
> (this is what I tested…).
> Regarding the characters æ and œ, the command \chr produces them correctly, that is
>
> \chr{ae} \chr{AE}
> \chr{oe} \chr{OE}
>
> produce
>
> æ Æ
> œ Œ
>
> as expected.
> If you think these commands are to stay, please tell me if they have to be on the wiki.
I uploaded a new version. You can run
s-characters-combinations.mkxl
to see what's there. I added enough to be able to meet Richard's
demands. Some in that list are a bit tricky, like
hook ȥ
stroke ø
because they are not really accents. The characters with hooks are not
officially build from two characters. There is no composition info so I
added that myself but in such a way that it doesn't interfere with
regular input. There might be more exceptions that we need to deal with,
but I just wait till someone bring it up (read: it's up to users to
come with additional specs).
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-02-09 13:08 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 [this message]
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=1a4b71ef-711f-50dd-0e3e-70e9769391c3@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=otared@gmail.com \
--cc=rmahoney@indica-et-buddhica.org \
/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).