Quantcast
Channel: Nginx Forum
Viewing all articles
Browse latest Browse all 53287

Re: Multilanguage Websites

$
0
0
On Mon, 31 Dec 2012 17:55:18 +0000
Francis Daly <francis@daoine.org> wrote:

> If you mean "separate content for each of language1, language2,
> language3; all available at separate urls", then you need no
> special web server cleverness after the user has chosen to go to
> http://language1.example.org/ or to http://www.example.org/language1/
> (depending on how you deploy it).

Yes at moment i have my webroot so
htdocs/de -> Default
htdocs/en
htdocs/fr
htdocs/ar

It need only be redirected.

> All you need is for the index page on the "main" web site to offer a
> series of links to each of the known separate language index pages.

The best way it is when it happens automatically. I find the language
selection boxes unappealing.

> Have a look at (for example) http://www.wikipedia.org/ or (as you've
> previously linked to) http://www.justasysadmin.net/

The CMS or wiki systems use different languages that's normal for the
Design and the use of the Software. I use never this Systems.

> If you want to implement some cleverness on the index page to avoid the
> user having to manually choose language, you must decide what you want
> the choice to be based on. Whatever you do choose, it may be worth your
> while making clear to the user why you chose that one, and what the user
> can do to get to the language version they actually prefer.
>
> The HTTP Accept-Language header is probably a reasonable choice, if your
> users know how to change it or to override it for your site.

We must again use this language selection boxes. Web 2.0 let's rock.


Regards
Silvio

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Viewing all articles
Browse latest Browse all 53287

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>