Re: status of /ust/lib/sgml -> /usr/share/sgml transition
Mark> 1. Entity References in Upstream Files (mods, dtds, ...)
Mark> Should we _always_ change the SYSTEM ids in entity definitions
Mark> to debian-specific relative paths, thereby assuming the user has
Mark> no catalog support. And when should we retain the PUBLIC ID?
Mark> Example:
Mark> In the case of the jrefentry.dtd [3], the upstream source
Mark> defines the full docbook xml dtd as the entity '%docbook' and
Mark> then references it as follows:
Mark> <!ENTITY % docbook PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
Mark> "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd";>
Mark> %docbook;
Mark> To be on the safe side, when I packaged this dtd I changed the
Mark> SYSTEM ID to a relative path and ditched the PUBLIC ID like so:
Mark> <!ENTITY % docbook SYSTEM "../../../dtd/xml/4.1.2/docbookx.dtd">
Mark> %docbook;
I think this is terrible. It means going along with the fact that XML
tools without catalog support are broken. Why should users of tools
that get it right (Jade) continue to suffer for that?
--
Ian Zimmerman, Oakland, California, U.S.A.
The easiest way to win an argument: ridicule your opponent's basic
assumptions by stating their negation and postfixing it with ", right?"
GPG pub key: 433BA087 9C0F 194F 203A 63F7 B1B8 6E5A 8CA3 27DB 433B A087
Reply to: