I am translating documentation for non-English users learning Docker. We have some example Dockerfiles with comments which we would like to translate for better understanding by the students. Are non-English languages, specifically Japanese, allowed in Dockerfile comments? If the students copy/paste the comments or try to type their own in a non-English language, will that create a problem?
Related
we are translating our website into several languages.
Since users can add the languages they speak (and other stuff) to their profile, we need a list of all languages (and the other stuff) in different languages.
Do you know if there are libraries that provide languages, countries, ... translated into different languages?
Thanks
I have several projects I've worked on that are setup for internationalization.
From the programming perspective, I have everything pretty much setup and put all of the string into an xml file or properties file. I wish to get these files translated into other languages, such as: Italian (it), Spanish (es), Germany (de), Brazillian Portugese (pt-br), Chinese Simplified (zh-cn), Chinese Traditional (zh-tw), Japanese (ja), Russian (ru), Hugarian (hu), Polish (pl), and French (fr).
I've considered using services like google translate, however I feel that this automatic translation tools are still a bit weak.
In summsary, I'm curious on if others have used professional translation services for their programs, if so which ones would people recommend and how did you coordinate the translation updates with the translation teams? Any idea on what I should expect to pay? Or is there a better way of doing this that I'm not aware of?
Machine translation services like Google, Bing etc. are not a good choice. As you mention, these services are in reality still in their infancy, and more importantly using them will most likely give your non-English customers a bad impression of your application.
If you want top quality translation, you will need to employ the services of a professional translation agency. Translators need to understand your application in order to translate the text correctly, so providing them with the application itself or screen captures of the English product will help.
You will pay per word - the rates vary from agency to agency, and also from language to language.
The other alternative is using crowd-sourced translations, from GetLocalization for example.
To summarize, proper localization is not just a matter of translating the text - you need to build a relationship with your translators, and ensure they understand your application and the context of the strings that they are translating, otherwise you will end up with a linguistically poor application, that will reflect badly on your company.
Does the Eventbrite SE stem words in languages other than English? If so, what languages are they and how is the language determined?
I did a quick check using the interactive docs here:
http://developer.eventbrite.com/doc/events/event_search/
Spanish-language stemming seems to work in many cases - since many Spanish words are pluralized by adding an "s" to the end. A search for "gato" and "gatos" both return the same result list.
From what I understand, SOLR's basic stemming support will automatically try removing or adding the letter 's' to the end of most search keywords. I think it does the same for other common english-language word extensions, like 'ing'.
Eventbrite is putting a lot of focus on i18n, and support for international events.
I would try testing several words from the languages that you would like to support. If you find the support for stemming in a particular language to be lacking, please pass your feedback on to the Eventbrite support team.
For a website like a marketplace or similar, what is the best approach for localization if majority of the content is in one language, but some user-generated content is in other languages?
There are so many approaches to this that I am getting confused, I am interested in the most cost-effective business optimal approach for this.
Some typical approaches;
Website in one language, accept content in many languages
Website in one language, only accept content in one language (reject other content)
Website in one language, content in the same language by translating to main language if content is not main language
Website in multiple languages, content is outputted as is for each localized version of the website, that is, content is duplicated for each language version of the website
Website in multiple languages, content belongs to the same language version of the website as the contents language is. That is, english content for english version of the website, german content for german version fo the website and so on.
tld vs subdomain vs directory for localization?
As others have commented, this is not really a technical question so is probably not the best fit here.
However, I will say that, if you are providing a service that has clients/users from different countries and different languages, basic politeness alone would dictate that you provide a website that can adapt to the client's language.
The content provided by the users in their own language should at least have an automated translation link (e.g. Google Translate).
If you don't do both of these things, you are locking segments of your possible audience out.
You also need to consider legislation. If you are providing services in some countries, it is mandated that you provide a number of base languages.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Coding in Other (Spoken) Languages
When writing code, do people from other parts of the world have to use the English language keywords for code written in things like .NET, PHP, SQL, etc? Someone else actually asked me this and after a few minutes of thought, I was actually stumped. The question was specific to writing SQL but is there a general rule of thumb? If a Russian developer who doesn't speak English wants to write some SQL, do they need to learn the "FROM, ORDERBY" etc in English? Are there parsers or are these languages "locale aware"?
People do not program in English. They program in a programming language.
Many of the popular languages use keywords taken from the English language, but you will see in many non-English countries variable names and comments that are in the native language.
So, someone may have to learn the keywords FROM and ORDER BY and understand their semantic meaning, but still have no idea about them being English (or how to pronounce them).
No modern language is localized in the manner you describe (i.e. parsers), so in effect, yes, they need to be learned in "English".