Support paths with non-Latin characters [#293026]

Comment #1

asak commented 12 August 2008 at 17:46

Title:

non-latin chars support...?

» Support for paths with non-latin chars

I've done some more thinking.

The same page on my site has the following paths:

www.x.com/node/22
www.x.com/מוצרי-חשמל/מנורת-שולחן
www.x.com/%D7%A9%D7%D7%9F-%D7%9E%D7%99%D7%9A/%D7%9C%D7%9C%-D7%93%D7%99%D...

The third once is interesting - While the link is displayed with the hebrew chars - the location in the address bar shows this format. google displays the correct heberw words in it's results.

Since i would not like to give up the hebrew paths, the only solution seems to be the third kind - Hoping the it will be possible to use something like this patch to enable to use of the % sign in the file path (is possible).

How can I make boost use the 3rd kind only?

It seems that boost is my only real option for caching...

Thanks ! ;)

Log in or register to post comments

Comment #2

asak commented 13 August 2008 at 18:23

Ok so I now read the readme file... ;)

* If your Drupal URL paths contain non-ASCII characters, you may have to
tweak your locate settings on the server in order to ensure the URL paths
get correctly translated into directory paths on the file system.
Non-ASCII URL paths have currently not been tested at all and feedback on
them would be appreciated.

I think my other notes can be called "feedback"...

Log in or register to post comments

Comment #3

Arto commented 25 October 2008 at 13:45

Title:	Support for paths with non-latin chars	» Support paths with non-Latin characters
Assigned:	Unassigned	» Arto
Category:	support	» feature
Priority:	Critical	» Normal
Status:	Active	» Postponed

Asa, unfortunately I have no idea how to achieve what you want as I'm not myself running any internationalized setup like this. This is definitely a legitimate feature request but needs somebody with a vested interest to figure it out.

If you or somebody else can come up with a patch to add support for non-ASCII characters (without compromising Apache security due to the escaped file names - there's a load of potential hidden issues here!), I will certainly include it. Until then, it's not very likely I will work on this, sorry.