[Wifidog] Localisation

Yanik Crépeau yanik at exScriptis.com
Mon Sep 27 16:46:49 EDT 2004

Hash: SHA1

Benoit Grégoire wrote:
|>In some jurisdiction, it could be illegal to rely on cookies to operate a
|>web site. This is the case in some landers in Germany and in at least one
|>canton in Switzerland.
| Do you have a link, I can't find ANY reference to this.  In any case such a
| legislation covering any and all cookies would be really, really stupid,
| Cookies targeting foreign servers are evil.  Other cookies are fine.

At the place I used to work, we got a lot of trainings. In such a metting, the
lecturer told us about Germany. When I was in Europe, another person told me the
problem is the same for German speaking Cantons. It was the case in 1999-2000, I
have not been updated since.

|>Localization issues have been addressed long ago during the http/html
|>standardization process. There is a standard html header that define the
|>language preference. User could set his/her language/locale preference
|>hiearchy. For instance, in my own copy of Firefox (a replacement for
|>Internet Explorer) I have set up languages/locales in the following order:
|>French/Canada, French, English, English/United States. That means that if a
|>localized version in French for canadian users is available, use it,
|>otherwise, if a French (international) version exists, use it and if no
|>fr-ca or fr exist, go to the English (international) and if none are
|>available try with en-us.
| True, but I've never bothered to set it, as it doesn't allow you to swich back
| and forth between languages.

Indeed, it DOES allow to switch between languages. You change the language order
and you reload the page.

|>It could seem complicated but support for this is pretty easy in most
|>http/html server available (appache, tomcat, php etc.). For plain html
|>files, in apache, it is just a matter of naming files. If the file is named
|>'index.html.fr', apache will use it instead of 'index.html' when it detects
|>a user with French as a prefered language. You could even go further with
|>'index.html.fr' and 'index.html.fr-ca' if you want to distinguish between
|>international French and localized French (using 'courriel' instead of
|>'mél' for 'e-mail' translation).
|>In my opinon, we should start the translation/localization process by
|>adding these files in:
|>	[cvs]/wifidog/wifidog-auth/wifidog/local_content/default/
|>	1) login.html.fr
|>	2) portal.html.fr
| I am far from certain this will work with smarty templates, and even so, the
| templates aren't the only things to translate.

It cost nothing to try. I have added the two files to the cvs server.

By the way, I also have added a cvs keyword to the four (4) files. When you add
the keyword "$Id: $" (forget the quote) somewhere in a file handled by CVS,
preferably on a comment section, the $Id:$ is expanded by CVS to display the
file name and version number as well with the name of the last person who has
commited the file. I simply have placed <!-- login page EN -- $Id:$ --> at the
beginning of login.html and a similar comment at the beginning of the three
other files.

|>By the way, is it possible to add me (yanik_crepeau) at the SF project with
|>write access to the CVS repository? Once done, I could handle the
|>translation/localisation of the two files (login.html.fr and
|>portal.html.fr) very quickly.
| Done



Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


Wifidog mailing list
Wifidog at isf.waglo.com

More information about the Wifidog mailing list