Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Offline
Re: Public-side multi-lingual URLs
I admit to not having read the entire thread, but I do think there are some cases where it is good to have localised urls, for example /author, /category etc. Currently I do this via htaccess.
TXP Builders – finely-crafted code, design and txp
Offline
Re: Public-side multi-lingual URLs
ax wrote #304355:
SEO likes URLs that would not change (as per language settings for example)
Maybe. The vagaries of search engine’s algorithms remain a mystery. In terms of language designators, I sort of agree. My initial draft when I started thinking about it was that having /en, /jp, etc in the URLs wasn’t much use. As long as the <html> tag has an appropriate lang attribute, search engines can figure out the language and index accordingly. Not having a visual URL designator makes things a whole lot simpler (in some ways) but more tricky in others. But it’ll largely depend on how we implement multi-lingual content.
Having localised URL components such as /category, /author, etc, I still don’t know. Part of me thinks it’s a nice-to-have. Part of me wishes I’d never followed the original Txp paradigm when I introduced context for the other content-types. It works fine for most Western languages, but looks terrible in browser bookmarks when they urlencode, for example, Japanese URLs.
Somewhere there’ll be a solution that satisfies most people, I just haven’t stumbled upon it yet.
What about having a voluntary advisory board for questions like this?
You mean, like a forum ;-)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Public-side multi-lingual URLs
Offline