Ticket #8690 (closed Feature Request: fixed+released)

Opened 5 years ago

Last modified 4 years ago

Any non-latin script should have Short Names available by default

Reported by: limi Owned by:
Priority: minor Milestone: 4.0
Component: Internationalization Version:
Keywords: Cc:

Description

Right now, the Short Name field is hidden unless you manually enable it. This works great as long as you are in a latin-based language where the normalizer works, but creates absolutely useless URLs for Japanese, Chinese, Arabic, Hebrew,Korean, etc.

If we can't figure out a better way to handle normalization for these languages for 4.0, I propose that we enable the Short Name field for all non-latin-based languages by default. In other words, if you have your site language set to Japanese, you have the Short Name field on all content.

Change History

comment:1 Changed 5 years ago by hannosch

  • Owner hannosch deleted

comment:2 Changed 5 years ago by hannosch

  • Milestone changed from 4.0 to Future

There's code to figure out the language of the user creating the site and actions can be taken upon that. I just tried to switch the 'visible_ids' settings to True and none of the actual edit forms changed in any way. So this feature is broken in more ways right now and needs a champion to pick it up.

comment:3 Changed 5 years ago by hannosch

I looked at supporting IRI's for a bit. Modern browsers actually support showing any kind of Unicode characters in the url bar of the browser just fine.

In order to support this on the Zope level in a sane way, we would need to ensure that all ids can actually be Unicode and not ASCII. Zope should handle the output/input encoding just fine. Technically the Unicode ID is encoded as utf-8 and then every character url quoted in the normal way (space as %20, ...). On the incoming side this relies on browsers to sent all url requests as utf-8 encoded. In IE6 this still needs a config switch to enable it, but in IE7 and all other modern browsers it actually is the default.

This might be an alternative in the mid-term to enable full Unicode URL's instead :)

comment:4 Changed 4 years ago by hannosch

  • Status changed from new to closed
  • Resolution set to fixed+released
  • Milestone changed from Future to 4.0

Following #9532 we have found a much better library to offer sensible transliteration for all languages.

Note: See TracTickets for help on using tickets.