For the best results when translating, it is important to always think about the context in which the source text was written and how it might be perceived if brought to the target culture. What this means is that language and culture are always very tightly intertwined with one another, so what one language might find normal, another language might find abnormal or outright offensive. For example, in the Hopi Indian language, there is no word for time, so their understanding of time is very different from most of the world where there is a defined word and definition for time. Similarly, divorce does not have its own native word in most Indian languages, and they instead use the English word “divorce,” if they ever want to get a divorce. However, divorce rates are much lower than they might be in other places in the world, due to their culture seeing marriage as a lifetime commitment. These kinds of cultural differences is why you have to do a little research when you are translating.

Similarly, in Japan, they have adapted a lot of English words into their own language and use them on a daily basis, but if an English speaking person heard these words, they might have a different idea of what they mean. For example the word “lamp” might mean a kind of light that you might find on your desk or in the room, but in Japanese, it is used almost exclusively for indicator lights. So when you translate languages that use words that appear in the target language as well, be sure to make sure that they have the same meaning in both languages.

Another thing you should be careful of is avoiding idioms altogether if you can help it. Idioms are commonplace in any language, but there will not always be an equivalent idiom in the target language. Unless the idiom is very essential to the translation, you should try to figure out a different way of phrasing it. For example, the phrase “two birds, one stone.” There may be equivalents to this in some languages, but if the target language does not have an equivalent, then you could instead say “accomplish two things with one action” or something of the sort.

While translation can be a fairly straightforward process of just taking the source words and then convert it into the target language, it can often be much more complex than that. While fields such as technical and patent translation might encourage a more one to one translation, there are some styles, phrases, and references that just won’t translate if you adapt a one to one style. That is where some creative liberties come into play where the translator tries to find replacement words or phrases that won’t always have the exact meaning of the original, but will be able to give the same nuance or elicit the same kind of reaction as the original did in the source language.

First, let us define what localization is. Broadly, localization is taking one material and transforming it into something that is understandable and relatable in a different culture or region. This means that localization is all about adaptation. When localizing something, you will be looking out for concepts, symbols, and words that would not fit into the target culture or region. This means adapting the original product into something that looks as if it was not created in a different country entirely.

For example, this can be something as simple as general design. When looking at an ad or commercial, for it to be successfully localized, you will have to make sure that the info displayed (i.e. numbers, date, time, etc.) are all changed into the appropriate format. If you kept the dollar sign when changing an advertisement for your product for an audience that does not use USD, they would be confused about how much the product actually costs and if it is even sold in the country that they’re in.

Internationalization is different than localization in that it focuses more on trying to universalize settings. Internationalization can be thought of as a typically more “under the hood” kind of process, where you will focus more on the coding side of things. This means focusing on hard-coded strings, concatenation, and finding out what is supported in Non-English input and output. If this is not taken into account, anything that is displayed is at risk to not display correctly. Internationalization is therefore more of a system focused on making sure that the software itself has no problem being used in different languages and thus focuses a lot less on linguistic errors like localization is.

There are more subtle nuances between internationalization, but it will be easy to remember the overarching difference between the two if you just remember that localization focuses more on the linguistic aspects of things while internationalization focuses more on the software that the localization will use to display or function.