Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A What word processor is recommended for writing a technical (programming) book?

You haven't specified any preferences for format (source or output), and that's going to be relevant. If it's up to you, for your source I recommend a text (not binary-format) markup language -- H...

posted 9y ago by Monica Cellio‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T04:52:22Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/20132
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T04:52:22Z (about 5 years ago)
You haven't specified any preferences for format (source or output), and that's going to be relevant. If it's up to you, for your source I recommend a text (not binary-format) markup language -- HTML, XML, LaTeX, or similar. A text source [works well with source control](https://writers.stackexchange.com/a/10443/1993), works with grep/find/search, and supports meaningful diff. All of these (assuming a reasonable XML DTD or schema like DocBook) support all the basic formatting you'll need for a programming book, including code blocks and cross-references. If you're formatting for the web then your HTML source is also your output (done!); for LaTeX or XML source or if you need to format for print (PDF), you'll need to run some sort of generator to turn your source into output.

Once you've decided on the format you can move on to choosing a tool. While WYSIWYG tools like Word and Open Office allow you to export various formats, choosing a tool that lets you write in your preferred format to begin with will be easier to manage. There are two basic categories of options:

- Your favorite text editor, if you are fluent in the format to begin with. It's actually quite reasonable to write HTML directly in emacs, for example. (You probably only need to learn 10-20 tags.) Downside: no syntax-checking; you can write invalid markup and the tool won't care.

- I'm not aware of LaTeX-aware editors. For HTML and XML, there are tools that help you with the syntax and make it hard or impossible to use invalid tags. Options range from inexpensive (Notepad++) to lower-cost (Oxygen) to higher-cost (Flare) to expensive (Arbortext anything). [This Wikipedia page](https://en.wikipedia.org/wiki/Comparison_of_XML_editors) compares features among a bunch of XML editors.

As noted earlier, for LaTeX or XML source you'll need to run a program to turn your source into an output format before you can inspect the results.

#1: Imported from external source by user avatar System‭ · 2015-12-18T04:10:36Z (about 9 years ago)
Original score: 4