We have an open bug for Red Hat that the fonts.conf DTD should
be registered in the system catlog so that, e.g., psgml mode can
Sounds reasonable to me. But fontconfig currently uses:
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
Using something along the lines of:
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
Would make it possible. (You don't really need both the public identifier
and the URL. I think you can omit either one, but I don't know the
syntax for omitting the public identifier offhand.)
You're way beyond my understanding of DTDs. Is there some formal body to
register public DTDs with?
I still have no idea how to make this work; can you present a more complete
recipe for this change?
This seems to be a useful link:
As far as I know 80% of the DTDs found on the web use whatever ID their author
cooked by itself. xsd is a bit saner, you can use URIs and DNS warrants they're
I read the XML 1.1 spec, both the identifier and the URL are required.
Regarding public-id's, the second part of this has a formal definition of the syntax: http://xml.coverpages.org/tauber-fpi.html
There are also examples in section 1.2 of this: http://www.faqs.org/rfcs/rfc3151.html
So I suggest one of these:
-//FDO//DTD Fontconfig Font Configuration Language @DTD_VER@//EN//
+//IDN freedesktop.org//DTD Fontconfig Font Configuration Language @DTD_VER@//EN//
+//IDN fontconfig.org//DTD Font Configuration Language @DTD_VER@//EN//
Where @DTD_VER@@ is incremented everytime the DTD changes. Copies of all versions should be available online.
I don't really know DTD, it is old, but I feel it does not require a resolvable URL anywhere
Fow xsds this is even more clear, take a look at "Should the targetNamespace be a URL or a URN?" on http://www.xfront.com/BestPracticesHomepage.html
When in doubt ask xml-dev on
The people here are nice and knowledgeable (they wrote the specs)
Looking at the catalog spec I'm not so sure it needs a different identifier. This question is probably best to ask on the xml list where people that write reference books can answer
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/4.