seefood

same here, and also with Hebrew. I’d guess this is a problem with Unicode in General. Mediawiki and WordPress translate those slugs well (I have Hebrew slugs for articles, categories and tags, they are ugly but they work like on Wikipedia).

I’m sure this is not a major issue for someone who knows his PHP (i.e. not me, ATM), and it’s fully backwards compatible with the latin1 slugs you support today.

Also, I was hoping using [[ wiki links ]] in blog posts would link to the pages or articles by the slug, but I see that posts are not actually parsed for wiki syntax – though I understand I can achieve a similar effect for now with another plug-in.

Is there a way to bump these feature requests? I prefer the wiki-in-WP for this project I hoped to launch this weekend, actually. Mashing up with a full mediawiki install is not difficult, but not as nicely homogenic, and I’d like to avoid it.

Here’s what I’ll do (tomorrow, because it’s after 1am).

since static.wp doesn’t have 2.0.5 I’ll find out when 2.0.5 was released and download the “daily build” for that day (I hope it’s not alpha code for 2.1!)

I’ll diff it from the 2.0.7

I’ll test if the patch works on the 2.0.5 Hebrew branch without hunks failing, which I will fix by hand if needed.

anything flawed with this logic? I’ll do it in about 8-9 hours, please enlighten me if there are other suggestions.

not a bad idea, but still, what about keeping https://static.www.ads-software.com/archive up to date? is there a CVS or SVN where I can check out an older version? […]

much appreciated!

seems like static has not been updated in months though… I need 2.0.5’s original tarball to check the diff, so I can make a patch to the Hebrew translation (which, for text directionality needs, has been a separate branch for a while now)