| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: run xmllint during build (was Re: need xmllint on borka) |
| Date: | 2014-08-21 20:18:45 |
| Message-ID: | alpine.DEB.2.10.1408212216220.21654@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> It is only run when the build is via XML/XSLT, not via SGML/DSSSL
>>> (because the SGML/DSSSL build already checks the validity anyway).
>>
>> I'm confused. I thought the point of this change was mostly that the
>> SGML toolchain is less strict than the XML toolchain, and you wanted
>> to have the more-strict checks applied whenever possible.
>
> The SGML tool chain is less strict about what it considers valid, but
> the XML toolchain doesn't check at all unless we run xmllint, it just
> produces garbage when the input is invalid.
This suggests that "xmllint" should always be run, because it is more
strict than the other, so it is safer if the source has passed it and is
validated, whatever the tool chain used afterwards?
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2014-08-21 20:28:28 | Re: run xmllint during build (was Re: need xmllint on borka) |
| Previous Message | Peter Eisentraut | 2014-08-21 20:12:57 | Re: run xmllint during build (was Re: need xmllint on borka) |