<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> As one with 10+ years with CSS, XHTML1.x and now HTML 5 I have to ask which versions of the XHTML specification you plan on supporting.<br> <br> I would assume you would target XHTML1.1 Strict and leave the notion of the XHTML 1.1 Modular alone as we've all departed on to HTML 5.<br> <br> Which brings me to the question, pdftohtml should include output to HTML 5, and since it's on all platforms perhaps one should utilize the WebKit HTML 5 Parser, especially since GTK+ and Qt are all in. GTK+ is even modularizing out their work so to separate the JavaScript engine to be reusable within other GTK+ projects.<br> <br> From GTK+ Changelog:<br> <br> 2011-06-20 Carlos Garcia Campos <a class="moz-txt-link-rfc2396E" href="mailto:cgarcia@igalia.com"><cgarcia@igalia.com></a><br> <br> Reviewed by Xan Lopez.<br> <br> [GTK] Split libWebCore into two libWebCore and libWebCoreGtk<br> <a class="moz-txt-link-freetext" href="https://bugs.webkit.org/show_bug.cgi?id=60539">https://bugs.webkit.org/show_bug.cgi?id=60539</a><br> <br> * GNUmakefile.am: Link to libWebCoreGtk.la too.<br> <br> ================<br> WebKitGTK+ 1.5.1<br> ================<br> <br> What's new in WebKitGTK+ 1.5.1?<br> <br> - The JSC library is now available independently. It's called<br> "libjavascriptcoregtk", and it comes with its own pkg-config file.<br> - New spellchecking APIs, useful to implement spellchecking features<br> in the UAs.<br> - New DOM methods to check if editable areas have been modified by<br> the user (webkit_dom_html_{input,text_area}_is_edited).<br> - Lots of improvements in the WebKit2GTK+ port.<br> - Lots of bugfixes.<br> <br> Since XHTML is a good citizen with HTML 5 I'd assume information on the WebKit HTML 5 Parser would be useful for the long haul.<br> <br> <a href="http://www.webkit.org/blog/1273/the-html5-parsing-algorithm/">http://www.webkit.org/blog/1273/the-html5-parsing-algorithm/</a><br> <br> If I'm off base, just ignore.<br> <br> Sincerely Yours,<br> <br> Marc J. Driftmeyer<br> <br> <br> On 06/21/2011 07:47 PM, Josh Richardson wrote: <blockquote cite="mid:CA26A5C0.2888%25jric@chegg.com" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <div>Experienced web developers always separate their CSS from their HTML file This makes maintenance and overriding of the styling much easier, as well as keeping the HTML file itself (nearly) completely content / semantics focused.</div> <div><br> </div> <div>In the complex mode, I would like to separate out the styling into a separate CSS file, referenced from the output HTML file. Any objections to this?</div> <div><br> </div> <div>I am also cleaning up the tags so that they are all balanced and XHTML, hence XML-compliant. Once this is done along with CSS separated out, I'm not sure of a need for a separate –xml mode for pdftohtml. Thoughts on this?</div> <div><br> </div> <div>Thanks, --josh</div> <pre wrap=""> <fieldset class="mimeAttachmentHeader"></fieldset> _______________________________________________ poppler mailing list <a class="moz-txt-link-abbreviated" href="mailto:poppler@lists.freedesktop.org">poppler@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/poppler">http://lists.freedesktop.org/mailman/listinfo/poppler</a> </pre> </blockquote> <br> <div class="moz-signature">-- <br> Marc J. Driftmeyer<br> Email :: <a href="mailto:mjd@reanimality.com">mjd@reanimality.com</a><br> Web :: <a href="http://www.reanimality.com">http://www.reanimality.com</a><br> Cell :: (509) 435-5212 </div> </body> </html>