From: Hans Hagen <pragma@wxs.nl>
Cc: <ntg-context@ntg.nl>
Subject: Re: Umlaut vs. diaresis
Date: Tue, 14 May 2002 15:20:51 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020514151310.02cd0a60@server-1> (raw)
In-Reply-To: <Pine.OSF.4.30.0205141224550.1289-100000@sirppi.helsinki.fi >
At 01:24 PM 5/14/2002 +0300, mari.voipio@iki.fi wrote:
>[This message includes lots of linguistics and quite little computing and
>ConTeXt and there are lots of special characters [esp. umlauts] in the
>text. You've been warned.]
Thanks for the explanation.
It is no problem to create a couple of language dependent feature sets (so
called language specifics) where we map for instance the diaeresis glyphs
onto umlaut or other ones; same for aring.
something like:
\let\adiaerisis\aumlaut
depending on the language.
We need to do this for your languages as well as german and/or others.
At the same time (to pick up an old idea) we can make a manual which
explains such language specific typographic features (also think of spacing
issues).
For that i need decent (non offending) pieces of text for testing and
demonstrating things.
How about that?
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next parent reply other threads:[~2002-05-14 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.OSF.4.30.0205141224550.1289-100000@sirppi.helsinki.fi >
2002-05-14 13:20 ` Hans Hagen [this message]
2002-05-14 10:24 mari.voipio
2002-06-05 18:08 ` Eckhart Guthöhrlein
2002-06-06 7:08 ` Hans Hagen
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=5.1.0.14.1.20020514151310.02cd0a60@server-1 \
--to=pragma@wxs.nl \
--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).