On Fri, May 24, 2013 at 11:10 PM, Kent A. Reed <[email protected]>wrote:
> > > Along those lines, I was thinking a while ago about how to streamline > the documentation process by using a workflow in which the PDF files are > generated and then HTML files are generated from the PDF files instead > of ... > .. the disadvantages I saw to the > current approach are: > > 1. maintenance of the two uses of asciidoc including disparate > stylesheets and processing options. > 2. subtle but obvious visual differences between the results in the two > formats. > 3. the difficulty of presenting mathematics in both formats from the > common AsciiDoc source (which may become a moot point with your work). > 4. there is a natual one-to-one correspondence between a logical > document and its resulting PDF file but an unnatural one-to-many > correspondence between it and its resulting XHTML files and supporting > files (stylesheets, javascript, image files,etc.). > > The documentation build is broken on Debain wheezy and jessie. Ubuntu and Debian (their TeX versions) handle Unicode/UTF8 differently. Things like the random non-breaking whitespace characters in the input '.txt' break the document build on Debian. And since the document build is monolithic with the code build ... Perhaps a good starting point for revisions to the documentation system would be deciding upon the character encoding for the source files? ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
