May 7, 2009 at 01:51Multilingualism
Colleagues,
and who solves the problems of multilingual content? subject to SEO of course and all other ryushechek!
My main postulates are:
1) Different languages on different subdomains (en.mainsite.com de.mainsite.com mainsite.com ––> default)
2) Automatic selection of the language for the client on the first visit (selection either by IP database or by language browser)
3) CNC with language specifics
4) All content in the other DBMSs
5) All media (pictures, etc.) live on a separate subdomain of media.site.com
6) In the skin, the language binding goes through the language file (loaded into the template) - from it’s easy to calculate the name of the subdomain in which language the file should be used (cache is already a separate topic, but is also being implemented)
and who solves the problems of multilingual content? subject to SEO of course and all other ryushechek!
My main postulates are:
1) Different languages on different subdomains (en.mainsite.com de.mainsite.com mainsite.com ––> default)
2) Automatic selection of the language for the client on the first visit (selection either by IP database or by language browser)
3) CNC with language specifics
4) All content in the other DBMSs
5) All media (pictures, etc.) live on a separate subdomain of media.site.com
6) In the skin, the language binding goes through the language file (loaded into the template) - from it’s easy to calculate the name of the subdomain in which language the file should be used (cache is already a separate topic, but is also being implemented)