permalinks structure not i18n friendly

should this be customizable via an options interface or via plugins or via i18n? I can think of even English-speakers who would want to change this, like /author/ => /artist/ or /contributer/ or something else, so maybe these should be options on the permalink options page.

I agree completely with markjaquith, and his way would probably make it easier to code, wright?

Attached patch allows for customisation of author, feed and comment feed bases. Although all these may not be necessary (and are thus superfluous options and thus harmful), I've left them in because

1. They can always be removed by the committor (easier to remove than to add them back in if someone decided we need them). 2. They might be useful for i18n (although we should allow .po/.mo files to customise these bases).

I don't think these need to be provisionable. Simply marking them for translation should suffice. In WP_Rewrite init():

$this->author_base = trim(__('/author/'), '/');

Slashes are included in the translatable string for context and then stripped back out.

This way the strings show up in the po files for translation, and we don't have to clutter the permalink page with settings.

Please don't forget the word "page", which is hardcoded in $pageregex (classes.php) and in $page_modstring and $page_modregex (both in template-functions-links.php). This word is quite important for translation because it is not an internet term like "feed", and it's meaning is the same as in other contexts.

Apply gettext to permalink structure elements

Patch attached that applies gettext to permalink bases.

I'm wary of this approach since permalinks will change if the translation is changed, making them not so perma. Persisting them in the DB means adding provisioning UI for all of these fields, which is ugly and annoying. Both approaches have drawbacks. Still debating the best way to go.

Sorry to insist on this, but the hardcoding of the word "page" as noted above is bearing children: please take a look at the last version (0.41) of the Permalinks Redirect Plugin: http://fucoder.com/code/permalink-redirect/ (line 83). If in the future the word gets marked lots of people will have their permalinks breaking. I just warned the plugin author.

I would like also to point out that the browser must support "strange" chars if they are in the translation on the permalinks. I don't think that a chinese char is supported in the address bar of the lastests browsers. Am I wrong?

My apologies for being a newbie at how to do this but I would like to vote for these two patches and suggest they fold into the next 2.1 alpha (3?)

The diff is for an old build so I am unable to apply to any 2.x version except for manual editing.

They test and work well, at least on my (US) english site.

I would also suggest a better ticket title, the ability to change permalink structure for "author" etc. is not just a language issue and would be handy to many.

Also note that the search_base can be potentially changed in 2.x

1762.diff

1. Ryan's patch reapplied to current trunk.
2. Use page_number_base to keep track of /page/

Note: change things and you'll have to update your permalink structure.

reapply ryan's patch to current code. page_number_base (update: fix typo)

I am +1 for making these options in Options > Permalinks. There are many times I wanted to change things like the feed base, the author base, or etc.

I think this is too broad for 2.2.

Okay, that's what I have so far. Feeds+comment feeds aren't working. If you try to click on a link in Kubrick, at the bottom, you'll see what I mean.

I'll keep debugging this in the morning.

This sounds like a very good idea.

Although I am not sure about overloading the Permalinks options page with extra options - maybe we should use filters instead and require a plugin to do the name changes?

Moving to 2.4 as it's too late to make a bit change like this to 2.3

Is the attached patch still valid?