* Tim Cross <theophil...@gmail.com> [2020-12-13 04:09]: > Given the move to HTML5 and deprecation of XHTML, how valid are > XHTML compliance requirements these days? Could it be time to > 'reverse' the org defaults and export using HTML5 by default rather > than XHTML?
There is no deprecation of XHTML, not until there comes XHTML5. And XHTML will remain for good number of years. It serves slightly different purpose and is more suitable for Org exports due to its rigid structure. XHTML must all the time be valid. Org export function should, when possible, or by user configured, include the validator check. It would not be good to switch to HTML5 because software does not produce XHTML well. It is better finding those bugs. > Would it be sufficient to just have the license information embedded > as a simple comment? Here are ways to make it compatible with LibreJS: https://www.gnu.org/software/librejs/free-your-javascript.html Jean
