153 reputation
8
bio website travisthetechie.com
location Ohio
age 31
visits member for 2 years, 11 months
seen Dec 6 '13 at 0:57

Open source, mobile, and cloud developer https://github.com/TravisTheTechie


Jul
13
awarded  Popular Question
May
27
awarded  Nice Question
Aug
8
comment Technical Writing Software
While unquestionably a valid answer, owning everything involved here would consume a lot of time I wouldn't be interested in spending. There are likely some XSLTs and CSSs file to be pilfered to get part of way there though.
May
20
comment Technical Writing Software
I'm not sure DocBook is the end-all myself either. But working with publishers, it's the most commonly desired format for the type of technical books I am targeting. Thanks for your suggestions though.
May
18
comment Technical Writing Software
It looks like the support is pretty broken for DocBook, from the link, "Currently it needs LyX 1.2.0 and it will not work with later versions of LyX." Additionally it links to a bug which has other bugs linked about this support. I don't think this would end up producing the output I want. However, I'll keep an eye on it, might be worth it if that gets cleaned up.
May
18
awarded  Teacher
May
18
awarded  Student
May
17
awarded  Autobiographer
May
17
accepted Technical Writing Software
May
17
revised Technical Writing Software
added 272 characters in body
May
17
comment Technical Writing Software
Thanks for your input Monica. It looks like Epic is totally overkill in it's current state. Some older versions appeared like they might be useful though. Oxygen I was also unfamiliar with and might be an option. I think it's time for to move beyond using vim now, there will be a lot of writing and having a more integrated experience might finally be worth it for me.
May
17
awarded  Scholar
May
17
awarded  Supporter
May
17
awarded  Editor
May
17
comment Technical Writing Software
I think the whole tool chain doesn't have to be easy. I'm okay with spending a little time building it out if needed. I think if I can easily produce structured content I can always come back and transform the content to another format with some clean up. PDF isn't my target output, like it was with LaTeX, since publishers will need to do at least some copy editing for the final format in question. Any "printable" output would only be for myself. Thanks for the responses, it provided more things to consider.
May
17
revised Technical Writing Software
Added OS clarification.
May
17
asked Technical Writing Software