Top Band
Multilinguist World 14 years of quality & guaranteed on-time delivery
you are here > Home Translation Services Website Localization
Bookmark and Share
Request a Quote

Website Localization

Multilinguist provides Globalization Consulting services organized around helping our clients to define and implement a globalization strategy that will result in faster international time-to-market and lower overall globalization costs. Our deliverable is a client-specific framework, methodology and value proposition for expanding globally at incremental, predictable cost rather than exponential cost surprises. With the integration of our product and service family into the development environment our clients are able to accelerate the global delivery of multi-language products and gain an edge over their competition.

Website Localization
Multilinguist translates a great deal of browser-based content, ranging from software applications with a browser interface to commercial websites.

Each of these projects is different in many ways, depending on the update cycle, internationalization status of the website, and requirements of the client. Multilinguist does not force customers to use a particular tool or methodology for website localization and updates. Instead, Multilinguist works with each customer to create a customized solution.

To create a website localization plan, Multilinguist typically collects the following information from clients, though this list can vary greatly from one project to another:
  • A complete directory tree of the live website files, either on a CD or in a zip file we can download. Though we could download pages from the website directly, we find it is often difficult to get all the pages, understand their relationships, and find all the server-based files.
  • A list of the pages and graphics to be translated. For example, some employment and investor information is probably not relevant to international users and some products may not be available worldwide.
  • Word counts of the text requiring translation. If you have this information readily accessible, it is very helpful in creating a proposal; if not, Multilinguist will count the words in the files provided.
  • Source files for the graphics requiring translation. Text in graphics can be much more easily localized when it is in layered files (such as non-flattened PSD files in Photoshop).
  • Related server-side files that require localization, such as text in Oracle databases, text output from ASP, CGI, ColdFusion, or JSP, etc. Any text that a user would see should be considered for localization.
  • Summary of databases used to generate the current Website and information about how international languages should be handled. Should Multilinguist localize the data in the database, or static HTML pages generated from it?
  • Information about how you want the existing links handled. Do you intend to keep any external links to different sites outside your own? Should they be changed to refer to localized pages, or noted that they refer to information in English?
  • Overview of the hierarchical structure of the international site. Do you want the localized site to use the same filenames and directory structure of the English site (which makes localization much easier, since no links must be changed)? How will users access the translated site (though a button or menu on your homepage, using a different domain name, or through some other link)?
  • Change management plan, including the frequency of changes you expect to make to the site. If you are planning on updates, we will utilize translation tools that "memorize" the work performed so any changes will be easy to make. It will not require a full retranslation of the work for updates to the Website.
  • Information about the localization status of any products referred to on the website. Do you offer products and documentation in other languages? If so, it will be important to ensure the localized web-based information is consistent in terminology and style.
  • Summary of testing expectations, detailing if Multilinguist should test the localized site on different browsers and platforms, and to what extent will be involved in the testing process.
  • Desired project schedule and final delivery date.
  • Reference material from previous localization projects, such as translated glossaries, previously translated text, and style guides
For more information about Multilinguist, website localization programs, and recommendations about international website management tools, such as those from MultiLinguist, please feel free to contact us
Bottom Band