Files Required for Website Localization

It is easy to assume that the files which appear on a website or browser-based software are sufficient for website translation but this is not the case.  This blog offers a list of files required for the  translation of server-side script applications that will help you get your localization kit right.

Often people download files over the Internet or save software files from a browser to create a localization kit of materials to be translated.   This approach often yields poor results for websites built with server-side scripts (ASP, JSP, PHP, ColdFusion, etc.). Instead, gather the server-side files for building a comprehensive localization kit and ensure all source code and database text are included.

Scripts for Active Server Pages (ASP) and Java Server Pages (JSP), as well as ColdFusion and PHP, use server-based software to create the pages that users see. The page a user sees through a browser is a dynamically-created document that often contains a mixture of a subset of text from the source file combined with content from a database.

To completely localize all the content necessary to use server-side scripts in target languages, it is necessary to start with the source files saved directly from the server directory tree, not when compiled for a specific browser session. The source files should include the script files (ASP, JSP, ColdFusion, PHP), the content database (Oracle, SQL, Access, etc.), and any graphics requiring localization.

If you have a WordPress or HubSpot marketing platform, you can also automate the language-to-language translation by connecting your site to SimulTrans.

Checklist of Files Needed For Localization of Server-Side Script Applications

1. Server-side script files (ASP, JSP, CFM, PHP, etc.)
2. Accompanying non-script browser files (HTML, XML)
3. Cascading style sheet files (CSS)
4. Back-end database content (Oracle, SQL, Access, etc.)
5. Enterprise software scripts and templates (eCommerce software, Enterprise JavaBeans, currency conversion utilities, etc.)
6. Graphics in layered, editable format (Photoshop, Fireworks, etc.)

Additional Reference Information

In addition to the appropriate files, it is often helpful to include additional reference information in the localization kit:

• Glossaries of terms in the source language
• Translated glossaries
• Product reference and overview information (though it may not be translated)
• Files of previously-translated versions and source files for the same previous versions
• Translation memory which can be leveraged for the project
• Style guide which addresses writing and design issues
• Information about the target audience
• Desired project schedule and final delivery date

Other Considerations

• How to deal with text expansion (translated text is up to 30% longer)
• Engineering and publishing contacts
• Summary of engineering expectations, including the build process
• Summary of testing expectations, detailing localization, internationalization, compatibility, and/or functionality testing requirements

Do you want to know more about the translation of website content? Check out this article on everything you need to know about website translation.

Ready to start your website localization project with a professional service provider with competitive website translation pricing?

This article has been updated and was originally published in August  2012