Apache OpenOffice (AOO) Bugzilla – Issue 67382
IZ fails to create pages that are valid x-html strict
Last modified: 2008-11-06 21:14:08 UTC
BUG/DEFECT because: CEE sets a default doctype of XHTML 1.0 Strict, but IZ fails to conform to it. (OOo used to have XHTML 1.0 transitional, but during the upgrade, it was changed to strict. (IZ doesn't properly encode the "&" in URLs as "&")
reassign to support
Hello @all, the change of default doctype of XHTML 1.0 to Strict makes no sense because our own bug reporting tool is'nt able to encode it. The other reason is, that a lot of pages was w3c-valid (transitional) an now there are not (strict). Please see also http://qa.openoffice.org/issues/show_bug.cgi?id=67322 Regars Marko Moeller
Have put in the same request to the engineers awaiting their response on this issue .
Stefan , Due to lack of resource in this component would be possible for us to defer the work in XHTML compliance for IZ .
ping? Any status update? If not, then Support: Please modify the default declaration in both your templates and on the current OOo-site.
Can you please try validating IZ page of Doc type XHTML 1.0 transitional and let me know if it works properly. I still see IZ page is not properly encoded even in XHTML 1.0 transitional. Regards, Kavitha Support Operations
Yes, as written in the first comment IZ doesn't encode the "&" properly. http://www.htmlhelp.com/tools/validator/problems.html#amp
Yes, true. Hence the request to have XHTML 1.0 transitional cannot be validated in IZ. Regards, Kavitha
st, Can this be marked as wontfix as this request of having XHTML compliance is not possible to validated in current CEE. Your thoughts? Regards, Kavitha Support Operations
Kavitha, the problem is, that we have the "x-html strict" in the header. This issue can be marked as fixed, if the webpages would have the "transitional" instead of "strict" in the header. We had this some time ago..
You ask "Can this be flagged wontfix" when you already wrote you will not fix it? What other status would be appropriate here? Again: Your operators changed the doctype to strict during the upgrade. Your product doesn't comply. It was asked to either comply to the set doctype or to change back to transitional. You did neither, in another issue 67322 we were told to change it back ourselves. That's what we did. Since CollabNet is not able/willing to make IssueZilla generate xhtml-strict, the only matching resolution is wontfix. But again: Please change your templates accordingly, so that you won't setup sites again that declare strict, but can not deliver strict.
close the invalid issue