Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Comments to Your points:</p> <ul> <li>single UTF-8 collation should do the trick for many languages but still You could have problems with arabic, russian, cyrillic, japan and chinese languages (input).</li> <li>there is no preferred lengths, it is just upon You. I use 50 chars for usernames, 500 chars for URLs and 250 chars for email addresses. But You also may let the user to choose a username with length of 300 characters - again, it is just upon You</li> <li>this has nothing to do with multilinguality and (somebody may suppose I am repeating mysels, but) it is upon Your preferrence</li> <li>not only the menu will change, You should also keep translated URLs with a mark which language is selected right away, thus the About Us page should be <ul> <li><a href="http://mysite.com/en/about-us/" rel="nofollow">http://mysite.com/en/about-us/</a> in english</li> <li><a href="http://mysite.com/de/uber-uns/" rel="nofollow">http://mysite.com/de/uber-uns/</a> in german</li> <li><a href="http://mysite.com/fr/a-propos-de-nous/" rel="nofollow">http://mysite.com/fr/a-propos-de-nous/</a> in french, etc<br /> therefore it is easier to keep the translated documents in a tree document structure where the homepage is on the top, <code>/en/</code>, <code>/de/</code>, <code>/fr/</code> folders and the content beneath but this leads to more difficult content administration. When saving the translated contents into a DB somebody may find switching between languages and following the previous URL to open up the right translated content with appropriate translated URL not quite easy, too.</li> </ul></li> </ul> <p>Conclusion: there is no preferred way of doing this and that when speaking of multilingual website - and that's the reason why there are no articles about the topic. Mostly it is about the CMS You are using and if You are writing one for Yourself it is only upon Your preferrences.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload