For example instead of "/node/add" we will have "/xxx/yyy" where "xxx" is translated word "node" and and "yyy" is translated word "add". And this for all words in paths and for all modules if there is translation for words or phrases used in paths.
For example instead of "/node/add" we will have "/xxx/yyy" where "xxx" is translated word "node" and and "yyy" is translated word "add". And this for all words in paths and for all modules if there is translation for words or phrases used in paths.
Comments
Comment #1
gábor hojtsyWho should do this translations? Should locale packs come with URL translations somehow? Or should the individual user set up these translations?
Comment #2
mki commentedIn my opinion, translation source should be the core/module/user, witch/who provading this path, e.g.:
http://www.example.com/admin - locale packs for core
http://www.example.com/user - locale packs for user module
http://www.example.com/custom_path - user providing translation
and combination, e.g.:
http://www.example.com/node/add/poll - locale packs for both node and poll modules
http://www.example.com/node/add/custom-content-type - locale packs for node and user providing translation
As we can see, translation should centre on slash-separated component of path (node, add, poll, custom).
Comment #3
Freso commentedSubscribing – and I agree that this should be shipped with Drupal('s translations), though it is too late to get this worked into D6. I doubt it'll fit nicely into the existing PO formats, and this either a new format must be used... or something else. I'm too tired to think much of this, but, yeah. As much as I'd like to see it in (at this moment, while half asleep), I say it'll have to wait for D7.
Comment #4
gábor hojtsyMoving to the language queue.
Comment #5
plachI am afraid this will have to wait for D8 :(
Comment #6
gábor hojtsyRetitling so it gives us a better idea of what this is about. I must add this does not look like will be a priority for Drupal 8 either. You can use custom URL inbound/outbound alters as well as pathauto to cover these needs in the meantime.
Comment #19
smustgrave commentedSince there hasn't been movement on this in 12 years I think it's probably not highly desired. Plus I feel the lift to convert everything to use translated paths will be heavy. Performance implications made?
If anyone disagrees please reopen.
Thanks.