pathauto will use content title for the url alias. However for asian languages, chinese, japanese, korean,
they are not Arabian kind languages, the path alias will be really odd if web browsers don't support utf url

is it possible to use english as the url alias ?
say

en/contact-us
cht/contact-us ie content title is in chinese traditional
chs/contact-us ie content title is in chinese simplified
jpn/contact-us ie content title is in japanese

Comments

dave reid’s picture

Status: Active » Fixed

The 6.x-2.x version is very similar to the 6.x-1.x version, but it supports using the Transliteration module which is exactly what you want for this purpose.

klonos’s picture

klonos’s picture

So, perhaps this is a duplicate to what I've originally requested in that issue? Please see my post where I believe I am asking for the same thing...

http://drupal.org/node/736178#comment-2694546

klonos’s picture

By the way... this issue is far from being 'fixed'. Transliteration doesn't help when languages involved don't use latin-like alphabet letters and even in 6.x-2.x there is no way of achieving what adrianmak asks for.

adrianmak’s picture

Klonos on #3 is talking what I want.

Is it a token or pathauto issue, or both ?

Freso’s picture

Version: 6.x-1.3 » 6.x-2.x-dev
Component: I18n stuff » Tokens
Category: support » feature
Status: Fixed » Closed (duplicate)

Transliteration is the practice of converting a text from one writing system into another in a systematic way. (Wikipedia)
In the case of the Transliteration module, it systematically converts non-Latin (really non-US-ASCII) text into Latin (or US-ASCII). So yes, the module is also for languages that do not use a "Latin-like alphabet". (It could be argued that it is particularly for those.)

However, the original request of using the source node's title is indeed a duplicate of #736178: Add a [node:source] token for source node of a translated node - so let's mark it as such.

adrianmak’s picture

I tried transliteration module on some other project and knew it deal with on non-lantin like alphabet like those asian languages

say for chinese like 聯絡我們, meaning of contact us, with transliteration module, it will convert to something like
lian-luo-wo-men. And for japanese, since there are hanji chars in japanese, the conversion will mix up of japanese pronunciation (ie hinagana) and chinese pronunciation (ie mandarian)

Be honest I don't prefer this kind of conversion and I prefer using English instead for a multilingual site with a language prefixed cht/contact-us

klonos’s picture

@adrianmak: lets continue this talk at #736178: Add a [node:source] token for source node of a translated node, I've copy-pasted your previous comment so lets take it there. Thank you.

@Freso: please see my comments at #736178: Add a [node:source] token for source node of a translated node

mrgoltra’s picture

subscribing. getting a page not found if title is in Japanese/Chinese/Korean character.

This is what I get this on the reports page

http://mysite.com/content/ad/%E3%81%93%E3%81%AE%E3%83%AA%E3%83%AA%E3%83%...

klonos’s picture

I bet you see this on IE only ;)

Anyways, this is agreed to be a duplicate of #736178: Add a [node:source] token for source node of a translated node

Please post your experience/questions there.