Re: [wgo] i18n url scheme (was i18n interface)

["Simone Deponti" <shywolf9982 gmail com>]

Uhm, you exposed quite a lot of problems.
I have only fiddled briefly with LinguaPlone, but I'll try to reply to any of your posts.

On 11/16/06, Gergely Nagy <greg gnome hu> wrote:

Note, this implies the URL wgo/about is never actually served, but
always redirected. However, links that want to point to localized
content should reference the "generic" url. Therefore, we could include
a "link to this page" element on every page, pointing to the generic
URL. Perhaps describe this linking policy somewhere on the site.

Requirement: such redirect must be cheap in plone.

I fear it wouldn't be too cheap. There are ways to achieve that, however (access rules, I'm thinking) and it shouldn't be too hard to implement for a seasoned Plone developer.
But I'd strongly discourage that path.

Furthermore, each page could include a link: view in my preferred
language (written in the users preferred language!). E.g. John Doe
arrives to a wgo page written in Chinese. "Select langage:" is written
in Chinese, and the dropdown shows "Chinese" written in Chinese,
therefore if he is not familiar with the site, he might not know how to
change the language.

BTW I'm assuming the language in the selection list appear localized.
(English, Deutsch, etc). All agree?

Yes, it can be done (it's a skinning problem). Note that if I go to see a content in czech, all of my page (except the "view this in <preferred language>" will be written in czech. As idea of usability, I'd prefer having the list of languages show each language name untranslated, eg.:

Deutsch
Francaise
English
Italiano
Espanol

This way, should be easier for the casual user to get back to the default language (he does not have a preferred language being anonymous) if he makes a mistake.

Error404:
---------

What happens, if the requested translation does not exist?

- display error message?
- redirect to preferred (default?) language?
- both?
- submit bug report?
- invite user to translate?

What about outdated translations? Is that an error? Offer to show
previous version? Use some heuristics to see how big the change was?
(e.g. original content diff size, or authors can mark changes as minor
or "not affecting translations") Or offer to show the change to the
user?

Summary, things to agree upon:

- URL scheme: wgo/$lang/foo
- lang negotiation priority
- the redirecting mechanism from wgo/foo
- language selection list
   - translated?
   - sorted?
   - extra items (automatic, preferred langs)?
   - extra items appear also in alphabetical list?
- non-existent translations

I don't know if LinguaPlone supports this, atm

Simone
-- 
<Ivyshaur> No, we've been informed that listening to Rammstein is the best way to learn German.
<mrPants> You learn it very quick
<mrPants> The problem is that you only know how to talk about sodomy, canibalism, incest, and death
<granola> there are other things to talk about?
<mrPants> Not in germany