TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Publishing / typesetting print documentation in HTML + CSS (+JS)
Subject:Re: Publishing / typesetting print documentation in HTML + CSS (+JS) From:Laura Lemay <lemay -at- lauralemay -dot- com> To:Jimmy Breck-McKye <jb527 -at- hotmail -dot- co -dot- uk> Date:Sun, 14 Aug 2011 12:25:46 -0700
People I know who are doing something similar to what you want are avoiding the browser altogether and using Prince (http://www.princexml.com) to go from XML+CSS to PDF. (it's not FO, it's easier than FO).
Laura
On Aug 14, 2011, at 5:05 AM, Jimmy Breck-McKye wrote:
>
> Does anyone here have any experience publishing paper documentation using HTML and CSS?
> Because my job involves testing and diagnosing problems in web applications, I've an awful lot of opportunities to learn about these technologies. It makes sense to learn one, versatile tool well rather than two poorly. It also makes sense to use technologies that are well-documented and easily understood by my peers. CSS helps me tick all these boxes.Practically speaking, I'm told that print CSS handling is quite mature on certain browsers, and from what I've seen, it looks as though CSS can do an awful lot. It also looks pretty straightforward to implement an XML - XSLT - HTML + CSS toolchain (as much as XSLT's syntax irritates me). Working in plain XML would free me to implement parts of my toolchain in other technologies, too (I've had especially good experiences transforming XML with Python scripts).But that's just the theory. Does anyone have any practical experience on this point? Any advice or common pitfalls?Thanks in advance,Jimmy/p>(Also, apologies if the carriage
> returns are broken. The Techwr-l mail handler seems to have a particular issue with my emails)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Create and publish documentation through multiple channels with Doc-To-Help.
> Choose your authoring formats and get any output you may need. Try
> Doc-To-Help, now with MS SharePoint integration, free for 30-days.
>http://www.doctohelp.com
>
> ---
> You are currently subscribed to TECHWR-L as lemay -at- lauralemay -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/lemay%40lauralemay.com
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
>
> Please move off-topic discussions to the Chat list, at:
>http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat
>
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
