Hi Erik,

Erik Ostrom wrote:
> [I sent this a couple of days ago, but it doesn't seem to have made it
> to the archive, which makes me think it didn't go out to the list.
> Apologies if you get it twice. The update is, I've fixed the first two
> issues, and some others, in my fork of the code
> (http://github.com/eostrom/typo/tree/master). Haven't pursued the
> BlueCloth performance problem.]

I did get this twice, but I don't see either the original or this version in the
archive either. How strange. Another message is showing up.

Anyway, thanks for working on the converter!

> Hi. I'm checking out Typo, with an eye to switching my WordPress blog
> away from it.

Yay! :-)

> [...]
>     * When I went to look at the post with 304 comments, it took long
>       enough that I opted to shut down the server instead. It's not
>       surprising that 304 comments would take a long time, but it turns
>       out generating HTML for just one comment takes roughly 30 seconds.
>       It was a long comment, but that's excessive.

That seems ridiculously long. Can you isolate this to a test case, as in, make a
little ruby program that just generates HTML for that one comment?

> I'd be happy to try to help fix any or all of these - I think I have a
> grip on the first two problems already. I wanted to get some guidance on
> a few things:
> 
>     * It seems the slow part of rendering those comments is BlueCloth.
>       First, I don't think these comments are even in Markdown (the
>       legit ones or the spam). It looks like the default in WordPress is
>       "HTML plus blank-lines-indicate-paragraphs". Should I just set the
>       filter for these comments to something else? (If so, what?)

You may have to write a little filter for that.

>     * Is BlueCloth really this slow? I noticed that last week marked the
>       release of BlueCloth 2, which speeds things up dramatically by
>       using Discount (written in C). Is there any interest in updating
>       Typo to include this new version?

If you can show us that the current version is slow, then yes, of course.

>     * There don't seem to be any tests for the converters, and I intend
>       to uphold that tradition. I also don't plan to get my hands on a
>       WordPress 2.5 database; I'm using 2.6. Should I just copy the wp25
>       converter to wp26, make it work for me, and leave wp25 alone?

I have no idea what the differences between 2.5 and 2.6 are, but if it's called
wp25 ... Anyway, I have no opinion on this. Maybe one of the other typo team
members can say something about this? Mephisto seems to just have a generic
wordpress converter.

Too bad there aren't any tests. If you can add some, that would be even better,
since I don't have any wordpress databases lying around.

Regards,
Matijs.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

Reply via email to