Altova Mailing List Archives


From: "Rick Jelliffe" <ricko@-------.---.-->
To: "xml development mailing list xml-dev" <xml-dev@--.--.-->
Date: 1/28/1998 12:21:00 PM
> From: Arjan Loeffen <Arjan.Loeffen@l...>

> So, in my opinion, following the replies to my earlier question, I think XML
> should start to support SDATA (as in SGML) and a way of allowing a system to
> determine what character the replacement text represents (which is 'covered' by
> public character sets in SGML).

Does anyone know what cunning plans the W3C font service people are up to?
>From my glance they seem to be looking for a way to distribute (= sell?)
fonts over the web, while we are looking at how to get a single glyph.
Anything XML does should fit in with them, I suppose.

Gavin Nicol started a group on this issue a little while back, but I think 
it was derailed by more immediate issues.

Certainly I think a PI system that "shortrefs" user-defined characters
to Xpointers that index into a font held remotely would be the best way.
Anyone like that idea?

Rick Jelliffe

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as:
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.