Remember the Y2K problem in 1999? Pretty much the same. Unfortunately, technology evolved so rapidly that they couldn’t keep up with the problem. So, basically, the US programmers did it their way, and the Japanese programmers, well, did theirs. This was all Star Trek to many, and most programmers wanted to find the quickest way possible: “ Let us deal with that issue in the future!” When the first computers and, eventually, coding systems were developed, no one thought about the internet, globalization, and smartphones the way we are using them now. You will mostly run into these issues when dealing with languages that don’t use the Roman alphabet. All they want to do is to promote their services/products to their audiences, while all the other side could see is a bunch of question marks and empty boxes. This is also a complete nightmare for clients as they are missing 100% of the shots they have taken. However, no matter how accurately you have written or translated those texts, if users can’t read what you have written, all your efforts will be poured into the drain. The correct technical terms, suitable language usage, and adaptive translation are some crucial factors needed to produce a successful localization project. Localization projects, as all experts know, require great attention to detail. Introduction to the Unicode Character Issue
0 Comments
Leave a Reply. |