Re: AW: Re: Russian Language Support

Dear Mr. Hoffmann,

thank you for the hint. We are using "DC.Identifier.URL.Node" for URL 
manipulation already but manually editing all the URLs wouldn't be very 
convenient for the users. In that particular case the site counts about 
450 single pages.

Anyway, thinking about the problem I was taking a look at some other 
russian sites like rambler.ru and found that they are using english 
declarative URLs. Same thing on chinese sites etc. - well - they have 
fare more special characters then us and no ASCII replacements. So there 
seems to be no useful way to deal with that problem.

The only page I found that really got a solution is wikipedia.org.
They are using Hex-Coded URLs like:
http://ru.wikipedia.org/wiki/%D0%97%D0%B0%D0%B3%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0%D1%8F_%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D0%B0

Even if this would would be very easy to do, I'm not sure if Hex-Code 
URLs are a good solution. They look very ugly - don't they?


Would it be possible to integrate an option flag into the language 
settings to selectively turn off declarative URLs or set them to a 
default language?

Kind regards
Tobias Greitzke




Dr. Frank Hoffmann schrieb:
> 
> 
> Thanks for the more detailed description and the example image.
> ZMS does not map _all_ the unicode chars to URL conformant strings. The log
> entry is due to missing character mapping of certain russian chars to
> 7bit-ASCII. This effect may be seen in Chinese, Farsi etc., too.
> 
> That is why it is recommended to use the meta element
> "DC.Identifier.URL.Node" for declaring URL/7bit-ASCII-conformant Strings,
> explicitly.
> 
> More about this topic:
> http://www.zms-publishing.com/support/content/e732/e736/e784/e1377/ 
> <http://www.zms-publishing.com/support/content/e732/e736/e784/e1377/>
> http://www.zms-publishing.com/support/content/e732/e736/e784/e2701/ 
> <http://www.zms-publishing.com/support/content/e732/e736/e784/e2701/>
> (only GER)
> 
> I hope the answer will help so far
> Best Regards
> fh, moderator
> 
> PS:
> Are there any code suggestions how to handle this a different (and still
> performant) way?
> 
> -----Ursprüngliche Nachricht-----
> Von: [email protected] 
> <mailto:zms-developers%40yahoogroups.com> 
> [mailto:[email protected] 
> <mailto:zms-developers%40yahoogroups.com>]
> Im Auftrag von Tobias Greitzke
> Gesendet: Mittwoch, 7. Mai 2008 22:34
> An: [email protected] <mailto:zms-developers%40yahoogroups.com>
> Betreff: Re: [zms-developers] Re: Russian Language Support
> 
> Changing back to id-based URLs fixes the error.
> In the log I find the following entry:
> 
> ------
> 2008-05-07T22:12:31 ERROR root
> [ZMSFolder@/zope02/zms_instance/content/e35/e3906/e5748/e5749][search_encode
> ]
> Traceback (most recent call last):
> File "/srv/zope/zope02/Products/zms/_zcatalogmanager.py", line 196,
> in search_encode
> s = unicode( s, 'utf-8').encode( 'latin-1')
> UnicodeEncodeError: 'latin-1' codec can't encode characters in position
> 50-57: ordinal not in range(256)
> ------
> 
> Using declarative URLs returns fragmented URLs like
> http://www.domain.tld///index_rus.html 
> <http://www.domain.tld///index_rus.html>
> 
>