[...]
> Have implemented your suggestion:
>
> http://code.google.com/p/asciidoc/source/detail?r=05257f9b440922e8971a1e313df036b2d3a629c4
>
> Putting this in the odt conf file should hopefully eliminate the need for
> the line_break.py filter:
>
> [miscellaneous]
> subsverbatim=specialcharacters,callouts,replacements3
>
> [replacements3]
> (\n|$)=<text:line-break/>\n
> \s=<text:s/>
>
Thanks Stuart
> OK I now think I understand the problem but I can't think of any easy way
> round this.
>
> The progress to date on the ODF backend is impressive, converting to ODF is
> a complex business, what I'm not clear on though are the benefits. From what
> I've read it seems to come down to finding a less complex way of styling PDF
The big idea as far as I was concerned was *interactive* styling.
> output than FOP offers, I'm just not convinced that the cure isn't worse
> than the disease.
Well, IMHO its getting towards that. As always the devil is in the
details and, until we tried it, issues like the nested blocks were not
visible.
Now, this is an unthoughtout idea :) What about keeping a stack of
nested blocks (well actually any nested element to be general) and
allow it to be accessed via a system attribute say {parent: [n]} to
access a particular parent (default immediate parent) and {has_parent:
<element-name>} to look for a parent of that name somewhere up the
tree and return its position. That allows things like:
{{parent:}@example:the extra markup if immediate parent is example} or
{{has_parent:example}?some more extra markup if example is somewhere a
parent}
>
> If this is the goal then wkhtmltopdf offers a much more straight-forward
> solution
> (http://groups.google.com/group/asciidoc/browse_thread/thread/94196f780ca3ad46):
>
> - You only have to style once for HTML and PDF outputs.
> - You style using familiar CSS stylesheets.
> - You can use existing AsciiDoc themes.
> - The wkhtmltopdf backend processor is fast, relatively light weight, and
> doesn't require a GUI to work.
> - wkhtmltopdf has pre-built binaries for both Windows and Linux.
Yes, I tried it when you first posted it (with the asciidoc user guide),
- I like the idea of CSS as the sole formatting language, at least one
commercial docbook processor does this
- As yet wkhtmltopdf isn't "book" quality so it can't replace
dblatex/fop, the worst offences are:
* page breaks inserted in random locations causing orphans and
widows and splitting tables in the middle of rows
* line wrapping didn't seem right
* I had font size and rendering problems (that may be just me :)
* links in the document don't work
- Unfortunately I suspect going through HTML loses too much
information to easily fix all of these
Cheers
Lex
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
