From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6821 Path: main.gmane.org!not-for-mail From: Taco Hoekwater Newsgroups: gmane.comp.tex.context Subject: Re: typeseting XML Date: Tue, 5 Feb 2002 14:20:28 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <20020205142028.73f2968a.taco@elvenkind.com> References: <5.1.0.14.1.20020205084513.039efaf8@server-1> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035397330 14088 80.91.224.250 (23 Oct 2002 18:22:10 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:22:10 +0000 (UTC) Cc: johannes.huesing@ruhrau.de, ntg-context@ntg.nl Original-To: "Hans Hagen" In-Reply-To: <5.1.0.14.1.20020205084513.039efaf8@server-1> Xref: main.gmane.org gmane.comp.tex.context:6821 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6821 Hi Hans, Hashes are very weird things, true. But the problem shouldn't occur. ConTeXt should insert a hashmark behind the scenes as soon as it discovers that the entity starts with a '9', or balk with an error message about an invalid entity. Entities that do not start with # are named entities, as opposed to character references. And names are not allowed to start with a number. Therefore, "&937;" is not valid XM. "Ω" is the correct way. Allowed alternative notations are "Ω" and "Ω". All may have any number of leading zeroes, and the XML spec also states that the character referenced itself should be a valid XML character (so � is also illegal) It would be much cleaner if there was a new command \defineXMLchar, that takes a number as argument instead of a csname string. Then the Context XML parser could have support for all of the possible inputs. Greetings, Taco On Tue, 05 Feb 2002 09:26:13 +0100 "Hans Hagen" wrote: > hashes are very special to tex, and once they end up in macro bodies they > spontaniously replicate etc etc -- groeten, Taco