This is Bugzilla
View Bug Activity | Format For Printing | XML | Clone This Bug
Looking at a file saved in AbiWord 0.9.2, I see the file format is as follows: <?xml version="1.0"?> <!DOCTYPE abw PUBLIC "-//W3C//DTD ABW 1.0 Strict//EN" "http://www.abisource.com/awml.dtd"> <abiword version="0.9.2" fileformat="1.0"> <!-- ... More AbiWord Markup... --> </abiword> There seems to be a few obvious errors in the <!DOCTYPE>. Firstly it defines the root element as <abw>, which it is not; secondly the formal public indentifier (FPI) associates the document format with the W3C, which is plainly wrong! I would suggest updating the root element and FPI to the following: <!DOCTYPE abiword PUBLIC "-//AbiSource//DTD AWML 1.0//EN" "http://www.abisource.com/awml.dtd"> However, I've also had a another thought for the future. For WAP 2.0, the WAP Forum defined their new version of Wireless Markup Language as a hybrid markup language. It re-uses XHTML elements such as <p> or <em>, and uses the concept of XML Namespaces for WML-specific elements, such as <card> or <refresh>. Here's an example document: <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//WAPFORUM//DTD WML 2.0//EN" "http://www.wapforum.org/dtd/wml20.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:wml="http://www.wapforum.org/2001/wml"> <!-- ... More Wireless Markup... --> </html> Could AbiWord, I wonder, also benefit from using an XHTML-based markup language? Suppose we assign an XML Namespace for AbiWord -- "http://www.abisource.com/2001/awml". Now, we take the existing XHTML specification, and use it as the basis for a second generation AbiWord Markup Language (AWML 2.0). As an XHTML host language, we also add the string "XHTML" to the FPI. It now looks something like this: <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//AbiSource//DTD XHTML AWML 2.0//EN" "http://www.abisource.com/dtd/awml200.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:awml="http://www.abisource.com/2001/awml"> <!-- ... More AbiWord Markup... --> </html> Any thoughts? Useful link: http://www.w3.org/TR/xhtml-modularization/ Thanks for your time, Dave
*** This bug has been confirmed by popular vote. ***
-fixed the 'abw' root element bug -we no longer use the w3c in our DOCTYPE description, so that part is invalid -added xmlns support now
No reporter/third party followup for at least 2 months. Assume problem fixed. If not, please reopen bug.
Sorry, a few more issues with the <abiword> element. Firstly, the actual AbiWord markup appears to be in the default namespace rather than "xmlns:awml". Secondly, the use of XLink attributes (e.g. when inserting a hyperlink into an AbiWord document) requires the XLink namespace to be declared. Consequently I believe this: <abiword xmlns:awml="http://www.abisource.com/awml.dtd" version="0.9.6-1" fileformat="1.0"> ... should be changed to this: <abiword xmlns="http://www.abisource.com/awml.dtd" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:svg="http://www.w3.org/2000/svg" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:math="http://www.w3.org/1998/Math/MathML" xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.9.6-1" fileformat="1.0">
good comment, someone should make the changes
fixed now
Fixed. Closing.
closing verified bugs whose target is no longer