michelv

An alternate solution is to open the .sql dump with a good text editor, and save it as utf8, then import it back into mysql.
Then you can just keep using UTF8 in WP 1.2.

This bug has ben fixed in the CVS version. Please be patient. ??

Not a bug.
In 1.2, you can edit the post’s slug (the %postname% part of the permalink) when you are in the Advanced Editing screen.
Since when you’re editing a draft you are taken to that screen, you can change the post’s slug just as you change the post’s title.

Tested, worked, committed.
Didn’t make it in RC1 because it was most likely not tested yet.

Release candidates are called candidates because they’re there to help fix the last showstopper bugs. Especially when they affect core functionality like pinging services.
That comment about free software was just trollish and uncalled for.

I tested in Gecko and got a weird character, I tested in MSIE and got an à instead of the í.
It looks like we’ll have to find a way to convert this character to its proper Unicode code point.

Search in the options.
The default was changed to utf-8, so you should change it back to iso-8859-1.
We may provide a script to translate your previous entries to utf8, but in the meanwhile it’s better to switch back to iso-8859-1 while your past entries rely on this charset.

Your friend is using a nightly build, and didn’t bother running upgrade.php.

Quand WP n’arrive pas à uploader, il donne une erreur.
Quelle est l’erreur ?

franpereiro: please provide a URL for your website/feed, so we can see what’s wrong. Just telling us “there’s a problem” isn’t enough information. ??
danithew: your feed has a blank line before <?xml, that’s why it’s broken. Check every WordPress file for a blank line after the final ?>, and remove the guilty blank line.

Just for the record, what was the last version you ran before the April 1st nightly?

Some posters missed the point of this thread.
This isn’t a bitchfest where you’re invited to target specific people, and nothing said here should be taken personally.
“I don’t like dotted borders.
– What? I use dotted borders, did you just call me a moron?”
This is bordering on ridiculous.
—
So this takes me to a bad blog trend: taking things personally.
If someone says he didn’t like the first Matrix, and you loved that movie, that doesn’t entitle you to react violently with “you suck”, high and mighty with “you have no taste for movies”, or my favorite, the anti-critics “where’s your movie, uh? can’t criticize!”.

I don’t really know what could be wrong.
Can you try posting a comment with as many spanish accents as you can, there?
(I already typed one and the i turned right…)

Both are known issues. Both will be dealed with in the next release. ??

Not a problem with WordPress.
Your feed is using UTF-8, but the site that aggregates the feeds does not support UTF-8 or other double-byte charsets (it does the same thing html_trans would do in WP).
Also, that site doesn’t even specify a charset.