From: "Johannes Hüsing" <hannes@ruhrau.de>
Subject: Re: typeseting XML
Date: Sun, 3 Feb 2002 20:51:05 +0100 [thread overview]
Message-ID: <20020203205105.A12482@ruhrau.de> (raw)
In-Reply-To: <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr.cz>
Hi all,
coming across a problem with encoding I searched my private
mailing list archive and found this question:
On Thu, May 17, 2001 at 01:54:54AM +0200, Petr Ferdus wrote:
[...]
> Also, would it be possible to have # char in the name of XML entity? Like:
>
> \defineXMLentity [#937] {$\Omega$} %instead of
> \defineXMLentity [937] {$\Omega$}
>
> because it seems to be rather conforming to naming convention of entities
> based on unicode position of its glyph (Ω in this case).
>
That would be a feature I would value very much. Has this been accomplished
already? I see ConTeXt in a quite confused state about the hash sign when
I try the above.
Greetings
Johannes
--
Johannes Hüsing There is something fascinating about science. One gets
hannes@ruhrau.de such wholesale returns of conjecture from such a
trifling investment of fact. Mark Twain
next prev parent reply other threads:[~2002-02-03 19:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 23:54 Petr Ferdus
2001-05-18 14:33 ` XML Petr Ferdus
2002-02-03 19:51 ` Johannes Hüsing [this message]
2002-02-05 8:26 ` typeseting XML Hans Hagen
2002-02-05 13:20 ` Taco Hoekwater
2002-02-05 13:57 ` Hans Hagen
2002-02-05 21:40 ` Johannes Hüsing
[not found] <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr .cz>
2001-05-18 14:10 ` Hans Hagen
2001-05-18 16:15 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz>
2001-05-18 16:53 ` Hans Hagen
[not found] <3.0.6.32.20010525212835.0127d390@server-1>
[not found] ` <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz>
2001-05-29 9:45 ` Hans Hagen
2001-05-29 14:05 ` Petr Ferdus
2001-05-30 15:01 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz>
2001-05-30 15:09 ` Hans Hagen
2001-05-30 20:12 ` Petr Ferdus
2001-06-14 23:07 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz>
2001-06-15 8:09 ` Hans Hagen
[not found] ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz>
2001-05-31 9:12 ` Hans Hagen
2001-06-01 8:03 ` Petr Ferdus
[not found] ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz>
2001-06-04 9:55 ` Hans Hagen
2001-06-06 4:47 ` Petr Ferdus
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=20020203205105.A12482@ruhrau.de \
--to=hannes@ruhrau.de \
--cc=johannes.huesing@ruhrau.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).