Adam Di Carlo <[EMAIL PROTECTED]> writes: > retitle 305736 non-standard XML ISO entity file names > reassign 305736 sgml-data > thanks > > Michael Smith <[EMAIL PROTECTED]> writes: > > > I guess it doesn't hurt, as long as the filenames of the *.ent > > files are consistent between the dbcentx.mod file and the filenames > > in /usr/share/xml/entities/xml-iso-entities-8879.1986/ > [...] > > So I think maybe sgml-data needs to be updated so that > > /usr/share/xml/entities/xml-iso-entities-8879.1986/ includes the > > filenames like "isoamsa.ent". They can just be made symlinks to, > > e.g., "ISOamsa.ent". > > I agree. I'll redirect this bug to sgml-data. I wonder why I was > using the upper cased versions in the first place.
I wonder why too :) Maybe because there's some other (non-package) that expects them in that form? Or maybe because the parameter-entity names that the DocBook DTD uses internally to refer to them follow that uppercase form. One thing to keep in mind is that up until DocBook 4.4, the DocBook DTD was using the form "iso-amsa.ent". DocBook 4.4 is the first to use the "isoamsa.ent" form -- because that's the form of the filenames that the W3C distribution uses. So seems like it'd be best have the DocBook package take the entity filenames for all the older releases and rewrite them in the W3C all-lowercase, all-one-word form. But I'm still wondering whether there might be other packages that expect the uppercase form. If so, seems like either you'll need to have both the lowercase and uppercase forms in the /usr/share/xml/entities/xml-iso-entities-8879.1986/ directory. Or the other package(s) will need to be updated to expect the lowercase forms. --Mike -- Michael Smith http://logopoeia.com/ http://www.oreillynet.com/pub/au/890
smime.p7s
Description: S/MIME cryptographic signature