Frequently Asked Questions

Internationalization refers to the development of software (websites, applications) taking into account, from the very beginning, that they will be launched in foreign markets. This enables faster localization and prevents errors and re-engineering.

For example, if you are developing an application in English but you know that you will also want it localized it into Spanish, you need to make sure that the OK button is big enough so that the Spanish term, Aceptar, will fit into the button. If you develop the button taking into account only the English term, once you have the translation you will have to redesign the button, and this is a waste of time (and money) that can be easily avoided.

Also, if you know that your application will be launched in Asian countries such as China and Japan, you have to make sure that your code supports double-byte characters.

There are many more aspects you have to take into consideration when developing your applications. At Jensen Localization we can give you some guidance to internationalize your software and we can also put you in contact with other companies that specifically handle content issues so that your content is ready to be localized.

Localization is adapting the source text to the language and culture conventions of the target language/country.

For example, if you are a company developing printers in the UK, the paper sizes specified in your printer driver will be in inches. However, if you want to sell these printers in The Netherlands, you will have to convert those paper types in cm, otherwise the users will not know which paper types your device supports.

It is the same with dates and time. USA and Italy have different ways of presenting the date and time. If you leave the US format, users may be able to understand that 05/25/11 means 25th May 2011. But what if the date is 05/07/11? Will they assume it is 7th May 2011 or will they think it is 5th July 2011? If they do not have another date as a reference like 05/25/11, they may get confused, and this confusion may lead to users stopping to acquire your products. So, why wait until this happens when you can easily avoid it by localizing your printer driver?

From the beginning of the computer age, United States has been the leading developer of software. Without any real competition, the corporations did not have to localize their products in order to sell and gain market shares. With the mass acceptance and large number of personal computers in the early 1980s, the percentage of software written by non-U.S. companies increased. It created competition which relatively did not exist before. Having coexisted in multilingual environments for centuries, European companies realized long ago the importance of localizing products before computers and software existed. Once they began to develop software, they were aware of the need to make the products available in the languages of the target market. Whereas localization has been a necessity for doing business in Europe, American companies needed to be convinced that their products have to be adapted before launching it to the target markets. The increasing competition of non-American software products in the global market have been pushing North American companies to localize.

There are classic examples of what happens when localization is done poorly. Everyone knows about the Mitsubishi “Pajero”, that for Spanish-speaking markets would have been a fiasco, due to the sexual connotations of this term (related to masturbation). Fortunately, Mitsubishi decided to change the name for marketing their vehicle in those markets to “Montero” before launching it.

The consequences of poor localization can range from the comical (creating a bad image of a company, the product or the service it is marketing) to the incomprehensible (making it, for all practical purposes, unusable). Also, bad localization can cause grief for unaware users by excluding important information from the foreign-language version (usually to allow it to fit in the space originally allocated for English). Consequently, American developers are better off leaving their information in English than creating a "quick and dirty" localized version.

As with most things, it's difficult to overcome a bad first impression. Sometimes you do not get a second chance, so do not leave your localization and internationalization needs in inexperienced hands.

Yes, we provide certified translation services for official documents like birth certificates, academic transcripts, and legal contracts.

It's fairly straightforward. Find experienced people to do the job. It does not matter if this is someone you hired as an employee or a localization service provider to whom the project is being outsourced. Make sure to have the right people for the job.

Secondly, be committed and allocate resources accordingly. Regardless of whether the localization is done by in-house resources or subcontracted to a service provider, a localization effort consumes time and personnel. A technical expert of the firm, someone who is familiar with the product, its architecture, the programming language and its functionality, needs to be available to the localization resources. Without the product expert, localization will take longer and the risks of errors are infinitely higher.

Thirdly, be responsive to the questions, feedback, and suggestions from the resources. They have a wealth of knowledge that developers involved in a first-time effort can take advantage of.

Finally, be realistic. The source product was not developed in three days; do not expect the foreign language version to be available overnight. Depending on the product and the components that are being localized, quality localization may take some time.

Ideally, you should start localization at the same time you develop your product. Although this may delay the development, you will know in real-time the issues your developers will have to sort out in order to support all languages required.

If you start localization when your application is final, you will probably have to do some re-engineering to accommodate all languages, and this will cost you time (and money).

We follow a strict quality assurance process that includes:

• Designating a dedicated Project Manager to ensure all processes are completed and we deliver the expected quality.
• Assigning native-language linguists with expertise in the subject matter.
• Performing QA processes.
• Using the last technology available to ensure consistency and that client’s requirements are met.
• Keeping close communication with our clients to adapt processes that ensure that their needs are met.

Our pricing varies based on factors like:

• Word count
• Language pair
• Complexity of the content
• Turnaround time

Contact us for a personalized quote!

At Jensen Localization we use the latest tools available in the market to process your files in order to deliver you the translation in the same format you used for the original files or in a format that will enable you to enter the translation in the original application.

We have an in-house IT-team that helps our Project Managers to solve any issue with your files without affecting the original schedule.

Jensen Localization guarantees the confidentiality of all received content. Jensen Localization is of course willing to enter a Confidentiality Agreement.