At 10:25 2002-11-06 +0100, Voigt, Ingo, NMG-FC said:
>>At 00:00 2002-11-06 +0100, Lennart Regebro said:
>>When doing language aware sites I think the language should
>>be selected
>>automatically from the languages selected in the browser, but
>>that it's also
>>important to have a possibility to select langauges manually,
>>by a drop down
>>box, for example. http://www.energy-plus.org/ comes to mind,

> your example has this done in a nice way. But there is also one way how this
> shouldn't be done. www.google.com, when I enter it with a german version of
> the browser I get redirected to www.google.de, no matter what. I would call
> that usability. Since in my understanding usability is about letting the
> user decide.

Next version of http://www.energy-plus.org/ (which will use EasyPublisher) will
choose initial language on browser settings.
But only when accessing through the top URL, e.g. if you have the preferred
language English (en) (you can have several but if English is the first that matches
those available on the Energy-Plus web site), you will be redirected to:
http://www.energy-plus.org/english.

From that point you can choose to access the French version instead by using the
drop down navigation, regardless of what the browser settings are.

I think this is the correct way to do it.


It will also incorporated some new feature to EasyPublisher like translation of messages and
support for RFC 3066 (ISO 639_1, iso_639_2, ISO 3166-1) and most important of all,
Language Synchronization support.

Language Synchronization support is necessary because it relieves the burden of
maintaining content in a multi-lingual site.

The fact is that all translations will almost never be done by the same person (if the person isn't a genies) .
There will be a need to synchronize changes in documents, this can off course be done by
sending scripts as word documents in the master language (preferably one that all translators will
translate from) between people using track changes to indicate what was changed.

This will get a quite big and complicated mess really soon, a mess that could and should be solved
by the CMS.
EasyPublisher works with one master language and an infinite number of slave languages.
(in fact it can use one slave languages as master for others, but it's not recommended.
Second generation translations always risks to be error prone and possibly slightly comical.)

Translators will get notifications when a master document has be changed and can
go to the web site and view the changes (a diff) of the master document.

Easy Publisher also handles synchronization of structure changes and binary objects
between languages.

Best Regards,
Johan Carlsson
EasyPublisher Team

--
Torped Strategi och Kommunikation AB
Johan Carlsson
[EMAIL PROTECTED]

Mail:
Birkagatan 9
SE-113 36 Stockholm
Sweden

Visit:
Västmannagatan 67, Stockholm, Sweden

Phone +46-(0)8-32 31 23
Fax +46-(0)8-32 31 83
Mobil +46-(0)70-558 25 24
http://www.easypublisher.com
http://www.torped.se

--
http://cms-list.org/
trim your replies for good karma.

Reply via email to