Make international slugs easier to edit

[options]

any non Latin-1 based Slugs are presented to a user in the precent encoded form:

1. they are unreadable;
   
2. hard to edit (unless you can do %-encoding right in your head);
   
3. getting truncated​ because of being overly long.

Steps to reproduce:

1. switch your keyboard to any non Latin-1 based language;
   
2. enter post/tagegory title;
   
3. try to edit it.

Solution:

just urldecode() slugs on output.

---

PS why WikiFormatting does not work here?

[options]

urldecodes() nicenames in Post/Page/Tagegories nicenames on output

[westi]

(In [7887]) Make international slugs easier to edit. Fixes #6915 props options.

[nbachiyski]

This behaviour was entirely intentional. Users don't like percent signs in their URLs and with this patch we are fooling them, that there won't be any.

This change would be a great plugin for the small percentage of people, who want their URLs full of percentage signs.

[westi]

(In [7891]) Revert [7887] see #6915.

[nbachiyski]

Patch, which allows to manipulate the slug, which the user can edit

[nbachiyski]

Attached a patch with appropriate filters, to make such a plugin possible.

[options]

first of all, thanks for the very fast reply and the hooks provided.

Replying to nbachiyski:

This behaviour was entirely intentional. Users don't like percent signs in their URLs and with this patch we are fooling them, that there won't be any.

while it's true that some users are a bit scared of percent signs in their IRIs, so that, for nothing better, they resort to ​renaming an every slug into numeric form (which is so '98).

however, are Google and my browser both fooling me by automatically decoding IRIs into the human-readable form?

no! instead, I'd call this a genuine focus on user comfort, usability and adhering to the standards.

This change would be a great plugin for the small percentage of people, who want their URLs full of percentage signs.

1. most of the people (just by default) use their national language in the slugs as a matter of fact (see picture above).

that said, such a plugin, unfortunately, won't solve the issue for the majority of WP users (using a stock install or .com hosted).

2. actually, only the small percentage of people can be bothered to transliterate -- let alone to translate in English (as some elitists do) -- an *every* post slug, thus trying to fool themselves and everyone else around.

[ryan]

(In [7896]) Add editable_slug filter. Props nbachiyski. see #6915

[joostdevalk]

That patch makes it possible to write a plugin, which makes it impossible to change the slug... It should only be possible to filter there if a name has not yet been saved, so something like this would work better:

{{{if ($name == $original_name) {

$post->post_name = apply_filters('editable_slug', $post->post_name);

}}}}

[joostdevalk]

hmm ok i meant:

if ($name == $original_name) {
  $post->post_name = apply_filters('editable_slug', $post->post_name);
}

[Denis-de-Bernardy]

Doh, sorry. I thought it was misplaced keyword.

Punting this back into 2.9, since you think it's a bug rather than an enhancement.

[options]

That's all right. Thanks for putting this back!

Now I wonder why Trac has begun to display (albeit partial) e-mail address in the CC field rather than login handle, as it used to do prior 2.8?

[Denis-de-Bernardy]

actually, it always has (best I'm aware anyway), when an email rather than a nick is entered in a cc field.

[dwright]

I just came across this ticket, there is a newer ticket filed for a seemingly similiar (same?) issue. I believe one of these could be a dup of the other, there is a diff (two) attached to the other.

​http://core.trac.wordpress.org/ticket/10966

[nbachiyski]

This one was fixed in [10108]. The other ticket has some additional problems, so we will take it from there on.