On 10/07/06, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
Hmmm... Maybe. But I don't see that this is ever going to be a generalized converter from HTML to OO. I see it as a step in a specific pipeline requiring quite good HTML. A very adaptable generalized converter will need mapping support between HTML and OO and that will be complicated. More complicated than I want anyway.
At least tagsoup allows xml (xslt) transforms? Hence the suggestions.
For example, I am publishing my CV like this. I maintain the CV in Emacs org-mode.
<grin/> shows good taste! From there I generate an XOXO microformat file which I
then XSLT into well marked up HTML (with DIVs and things). I can then use html2oo.xslt to tranfer that into OO and from there get Word or anything else that OO can spit out.
Sorry Nic, I'm not a micro formats user I'll spend some time with the stylesheet, see what comes out? regards DaveP
But now I would just have a single HTML design with a CSS providing the look for the web pages and html2oo.xslt producing Word (via OpenOffice).
I guess I'm more cynical than you? I was thinking html in the wild?
Anyway... I've inlined the stylesheet at the bottom. As I said, it's not comprehensive yet but as I need more elements I will add them. Right now, I'm controlling the resulting OO file with a Makefile that looks like this:
Ouch. You found one of my blind spots. make never meant anything to me
There are options for making this better but it kinda depends on what tools you want to use for the XSLT.
My preference (surprise surprise) would be to stick with xslt.
If I setup a darcs (http://abridgegame.org/darcs/) repository for this would anyone contribute do you think? Would you?
I'll try anything once! let you know.
<?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0"
<snip/> -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
