I signed up to the translation project and started immediately to translate but the common problems for the translations to Turkish came up soon.
I will try to explain the problem with an example:
The order of words in lots of phrases in Turkish are different.
For example, if the "date" is a column in a table and you want to sort table by this column, you simply say:
"Order by date"
In Turkish, same phrase is:
"Tarihe gÃƒÂ¶re sÃ„Â±rala"
I can write down the relations (not translations!) between words in two languages as
Order => sÃ„Â±rala
by => gÃƒÂ¶re
date => Tarihe
"date" means "tarih" but there is a suffix "-e" to make the same sense and it comes to the first place in the phrase and therefore should start with a capital letter (if it is required).
In translation server only the "Order by" part of the phrase are given and it cannot be translated as "gÃƒÂ¶re sÃ„Â±rala" to Turkish because it will be "gÃƒÂ¶re sÃ„Â±rala tarih" when it is shown in the frontend with the name of the column. It can be solved by translating it like "SÃ„Â±rala: " and the result in frontend will be "SÃ„Â±rala: tarih" but it is actually saying like that "Order by criteria: date".
The simple solution is ofcourse,
"Order by %s"
It solves many of the problems, not all! :) but we can leave it with a capital letter problem because it is an i18n issue, not a SS issue.
Some texts which have the same issue and solutions:
"Welcome to the" => "Welcome to the %s"
"No images found in" => "No images found in %s"
"Change to" => "Change to %s"
I cannot make a whole list of them but the general rule should be as follows:
"If there is a preposition in the text, use %s"
I like SS and want to give a chance to make it my primary CMS as a developer. i18n and l10n are important topics to spread it as well as the number of built-in and community supported extensions and documentation.