You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have developed a new experimental feature that allows the outputting of
multiple [X]HTML files.
The feature effectively allows you to insert page breaks & specify the
file-name & title of the new page.
The user simply adds lines of the form "%!output: <file-name> <page-title>" to
their source file.
Whenever txt2tags encounters this it creates a new output file & handles
writing headers, footers etc.
Subsequent output is directed to the new file.
It also correctly creates any table of contents so links point to the
appropriate files.
I've also added support for "%!meta: <name> <content>" which adds 'meta' tags
to the header of the current output file.
Combined these features allow the easy generation of help books for Mac OS X.
[My primary focus.]
If there's any interest I can supply a patch. The code is based on svn HEAD.
It also includes a few other small changes including the ability to specify a
CSS class for each table instance.
Original issue reported on code.google.com by chris...@gmail.com on 12 Jun 2010 at 4:33
The text was updated successfully, but these errors were encountered:
OK here's a patch I just created against r117.
Please note that it is experimental & I'm only a pretend Python programmer ;-).
Having said that, I've had no problems with it though I've only tested it with
the following options:
txt2tags -i <source-file> -o main.html -v
and
%!target : xhtml
%!encoding: UTF-8
%!options : --toc --enum-title --css-sugar
%!style : style.css
…
with Python 2.5.1 on Mac OS X 10.5.8.
Not everything in this patch is necessary for this particular feature.
It also includes the facility to place <p> & </p> on the same lines as their
enclosing text as that then makes it possible to add custom <div> blocks (etc.)
via postprocs.
Original comment by chris...@gmail.com on 18 Jun 2010 at 4:46
Original issue reported on code.google.com by
chris...@gmail.com
on 12 Jun 2010 at 4:33The text was updated successfully, but these errors were encountered: