Pozdrav Dalibor, Yes precisely, that's the point I wanted to make to, as you did.
As a famous writer wrote, no matter if our languages are almost the same, I stand for the rights of others to have their language named in their language, but I refuse to be deprived of the right to have my language named by its name (which is internationally recognized). Consequently, as you state, pages in Serbian, Bosnian, Montenegrin, should be marked as such. The technical point I guess is that Google reacts according to the largest amount of data that it has. That is called parallel data. In other words, Google has more translations in its database in Croatian than in Serbian and Bosnian and Montenegrin together and therefore always suggests Croatian instead of using the locale, i.e. .sr, .ba, etc. That is actually awkward since uploading any translation entry into Google requires that you name the locale. That could be a good solution to that issue. We all know that ex-Yugoslav languages (except Macedonian and Slovenian) are almost the same, but it is your fundamental right as well as mine to have our languages named by their actual name. I am sure that Croatian speakers share that view. For example, the "new" generation in Croatia doesn't use or learn the cyrillic script. I guess they wouldn't appreciate a web page in cyrillic script to be called Croatian... If you visit a website like www.capital.ba, you will see a Bosnian website written in "Bosnian Serbian" (Serbian but using "ijekavski" and not "ekavski" like in Serbia. Glad to share with you on these points. It's a pity that we get no or very few Google feedback on these questions. Take care, Senad PS: If you haven't read it yet, here is what Google states about parallel data: (https://groups.google.com/forum/?hl=en&fromgroups#!topic/google-translate-general/tVyrIsVu2Kg) Hi everyone, Just about every day we hear from a user, or potential user, asking us when or if we'll support translations to/from language X. While we're quite proud that we already support 52 of the worlds languages, there are still many more languages that we would love to enable for our users. We're constantly working hard to bring new languages up to our quality standards so that we can make them available to our users, but unfortunately launching a new language is hard. Every language that we support requires very large amounts of training data and significant amounts of engineering work to make available to you, our users. So if we don't support your language yet, rest assured, we're working on it. The limiting factor is almost always training data. What we need is large amounts of parallel data, that is, large amounts of documents or sentences that have already been translated between the new language and one of our supported languages. The best way you can help is by contributing Translation Memories (TMs) or glossaries by uploading them to Google Translator Toolkit (http://translate.google.com/toolkit). For details on how to contribute, see the following: Uploading a Translation Memory: http://translate.google.com/support/toolkit/bin/answer.py?hl=en&answer=147844 Uploading a Glossary: http://translate.google.com/support/toolkit/bin/answer.py?hl=en&answer=147853 If you don't have existing TMs or glossaries to upload, but are multilingual and still want to help, you can contribute by using the Translator Toolkit to translate documents into or from the new language you hope we'll support and allowing us to use the data you create to train our systems. Many thanks everyone. Cheers, Josh Senior Software Engineer Google Translate -- You received this message because you are subscribed to the Google Groups "General" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-translate-general/-/Qlun4j7LoaAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-translate-general?hl=en.
