The script and tricks in the ODF scripting section of this website show how to create office-ready texts, presentations and spreadsheets automatically, in the OpenDocument format, which is a worldwide standards. This is all many people need to work today. Sometimes, however, it’s still necessary to either print those documents, or exchange them to somebody in other formats, like PDF or those of the older releases of Microsoft Office (newer releases of this program are already partially compatible with OpenDocument through free plugins, so if your partners have those versions they should really use those plugins, instead of bothering you with requests for drug-like, legacy file formats, but that’s another story).
- This page gives a general overview of a flow for transforming ASCII files in print-ready PDF books. The reasons for setting up such a flow in this way are explained in the first part of this tutorial. Basic workflow The basic usage of txt2tags is really simple. Once you’ve written something that you need to convert to PDF, text or HTML you can launch the graphic interface with the -gui option or run a command like this at the prompt:
- This is the core script I used to transform a set of plain ASCII files with the Txt2tags markup in one print-ready PDF file. Part 1 of this tutorial explain why I chose txt2tags as source format and Part 2 describes the complete flow.Book creation workflow Listing 1: make_book.sh 1 #! /bin/bash 2 3 CONFIG_DIR='/home/marco/.ebook_config' 4 PREPROC="%!Includeconf: $CONFIG_DIR/txt2tags_preproc" 5 6 CURDIR=`date +%Y%m%d_%H%M_book` 7 echo "Generating book in $CURDIR" 8 rm -rf $CURDIR 9 mkdir $CURDIR 10 cp $1 $CURDIR/chapter_list 11 cd $CURDIR 12 13 FILELIST=`cat chapter_list | tr "�12" " " | perl -n -e "s/.
- Many people write far more now that they are constantly online than in the pre-Internet age. Most of this activity is limited to Web or office-style publishing. People either write something that will only appear inside some Web browser or a traditional “document”, that is a single file, more or less nicely formatted for printing. Very often, however, they don’t do it in the most efficient way. The most common solution for the first scenario still is to write HTML or Wiki-formatted content in a text editor or, through a browser, directly in the authoring interface of CMS systems like Drupal or Wordpress.