On Fri, 24 Jun 2011, Martin Budden wrote:
Question: why do you want to post-process the HTML rather than fix the
wikifier so that it generates paragraphs rather than tags?
a) Because in the context I'm working in, I don't have access to the
wikifier.
2. Because I'm intellectually curious a
Question: why do you want to post-process the HTML rather than fix the
wikifier so that it generates paragraphs rather than tags?
On 24 June 2011 14:15, wrote:
>
> As anybody who has inspected the HTML generated with tiddler.text is
> rendered to HTML, TiddlyWiki doesn't create perfect HTML. Th
On Jun 23, 9:36 am, rakugo wrote:
> My question is where does the line get drawn about what can be pushed
> into the project as we have a duty to project the code base for
> existing users.
Since Github has Github pages, I think it would be nice to have some
links there.
Links to tiddlywiki.com -
On Jun 24, 3:15 pm, chris.d...@gmail.com wrote:
I saw purpleater which looks quite promising :)
> My question: Has anyone come up with a good way to post-process this
> HTML so that it can be used as a reasonable DOM (such that paragraphs
> are paragraphs etc).
I did 3 attempts allready. (Your an
Hi Chris
> My question: Has anyone come up with a good way to post-process this
> HTML so that it can be used as a reasonable DOM (such that paragraphs
> are paragraphs etc).
The Readability project has done a lot of work around this
(http://code.google.com/p/arc90labs-readability/).
Ben
--
As anybody who has inspected the HTML generated with tiddler.text is
rendered to HTML, TiddlyWiki doesn't create perfect HTML. The biggest
standout problems is that instead of making paragraphs, it separates
blocks of text with tags, sometimes 1, sometimes 2, depending on
the number linefeeds pr