[CALL FOR REVIEW] Upgrading to DocBook 5.0
Hi, during the last weeks, I've been working on upgrading our documentation set to DocBook 5.0 and a higher-quality PDF generation toolchain, sponsored by the FreeBSD Foundation. With FF, we have discussed that high quality print output was especially important because of the upcoming print edition of the FreeBSD Handbook. The best tool available for this was Apache FOP, which is Java-based. Java is only required for high quality print output but not for validation of documents and XHTML generation. Since some committers are concerned about depending on Java, I've also added support for dblatex, but it is more limited. The deliverables of the overall work are: 1, A DocBook 5.0 tree of the documentation. The basic set is available in projects/db5 but still the converter has to be run on a fresh checkout. The converter can be obtained from user/gabor/db5 and it has a README, which explains how it works. The converted sources are not checked in because in this way merges are easier and adjustments of conversion parameters is still possible until we merge this to head. 2, A FOP-based rendering toolchain. This gives high quality output and after some last touches it will be print quality. I18N support is really good, all languages can be rendered in high quality, even CJK languages. A full PDF build can be found here: http://kovesdan.org/files/fop/ 3, A dblatex-based rendering toolchain. This toolchain is more limited. Its customization is more difficult and non-Latin text is not wrapped properly. Also, it fails with programlistings in tables so it cannot build the whole documentation set. This is a limitation that is explicitly listed in the dblatex documentation. This is a Java-free solution but it does not give us full support and such a high quality as FOP. Some sample documents can be found here: http://kovesdan.org/files/dblatex/ To get the sources, you can checkout the db5 branch and the converter from user/gabor/db5 and run it in the top-level directory of the doc sources. Or you can grab my snapshot: http://kovesdan.org/files/doc-db5.tgz To use this tree, you need for all output types: textproc/docbook-500 textproc/docbook-xsl-ns For PDF build in general: chinese/arphicttf japanese/ipa x11-fonts/gentium-plus x11-fonts/droid-fonts-ttf x11-fonts/lohit To test FOP build, you additionally need to install: textproc/fop To test dblatex build, you need: print/texlive-full textproc/dblatex To build PDF files with dblatex, run make FORMATS=pdf all. To do it with FOP: make FORMATS=pdf RENDERENGINE=fop all. Please let me know about your comments. I plan to merge this changeset when I'm back from vacation, after Aug 12. Gabor ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: [CALL FOR REVIEW] Upgrading to DocBook 5.0
On Fri, 2 Aug 2013, Gabor Kovesdan wrote: 3, A dblatex-based rendering toolchain. This toolchain is more limited. Its customization is more difficult and non-Latin text is not wrapped properly. Also, it fails with programlistings in tables so it cannot build the whole documentation set. This is a limitation that is explicitly listed in the dblatex documentation. This is a Java-free solution but it does not give us full support and such a high quality as FOP. Some sample documents can be found here: http://kovesdan.org/files/dblatex/ This looks pretty good. There is a problem in that paragraphs are indented inconsistently. See the Committer's Guide, "3.1 Introduction" for an example. The first paragraph is not indented, following ones are indented. Thanks for your work on this! ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: pcb production from china
Dear Customer This is Jun from Jxtpcb, Our company is one Printed circuit boards value-added services provider in China. 1. Quick turn pcb, Prototype pcb( 12- 72 Hours Fast Delivery ) 2. Rigid pcb, Flexible pcb(Fpc), Rigid-flex pcb, LED pcb, Metal base / core pcb, Microwave / high frequency pcb etc... 3. High quality products, Competitive price, Professional services, Fast delivery 4. No MOQ We will very pleased to supply you any information about our products, kindly feel free to contact me. Thank you! --- Best regards Jun Lee Tel: 86-755-29760917 ext. 605 Fax: 86-755-23283744 Msn: jxtchinasal...@hotmail.com Skype: jxtsales1 Email: sale...@jxtpcb.com Web: www.jxtpcb.com P please consider the environment before printing ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: [CALL FOR REVIEW] Upgrading to DocBook 5.0
The FOP output looks real nice. A few things though: 1. It appears that the links to svn revisions do not work. The FAQ book has an example of this in the question "Does ZFS support TRIM for Solid State Drives" (pg. 51). 2. Author attributions (chapter 3 heading in the handbook, pg. 13) unnecessarily take up an extra line for the email address. 3. Text within "literal" tags are truncated to line endings via hyphenation. FAQ book question 4.4.1 has probably the worst type of example for this, where "allscreens_flags=" is transformed into "allscreen-s_flags=". It is worth noting that if you actually copy and paste the text, some pdf readers will intelligently remove the hyphen (foxit does, evince does not). 4. Boxes produced via "example" tags can get split between pages (see pg. 64, 65 in FAQ). I think "warning" and "note" boxes are not affected: pg 44/45 in FAQ have a "warning" box and and empty space on the previous page. 5. Justification is producing an unnecessary amount of hyphenation. A good example of the number of hyphenations used is on page 35, where 4 out of 7 line breaks require hyphenating the word at the break; and an example of the bad type of hyphenations is on 1.1 (page 1) of the FAQ where "enhancements" is broken into "en-hancements". I am not really sure how it is possible to tweak this (This is entirely subjective, but I believe I'd prefer a requirement of 4 or more characters preceeding the hyphen), but from a small case study (fedora's installation guide [1] and debian's new maintainers' guide [2]), they have a greater amount of text per line (debian: 116, fedora: 106, freebsd: 84), which I assume gives more leeway for the formatter to reduce hyphenation. [1] http://docs.fedoraproject.org/en-US/Fedora/18/pdf/Installation_Guide/Fedora-18-Installation_Guide-en-US.pdf [2] http://www.debian.org/doc/manuals/maint-guide/maint-guide.en.pdf ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
