pimg width=400 height=249 align=right alt=JVIS src=http://drupal.org/files/home-en.jpg hspace=5 vspace=5 /a href=http://www.jvisusallc.com/JVIS USA LLC/a is an international supplier for automotive components and tooling with facilities in 6 countries and customers all over the world. Their website helps them introduce their products to auto makers./p h3Going multilingual/h3 pWhen JVIS commissioned their website, they requested just a few static pages. It was built as a simple static HTML site (no CMS) and in English. Very soon after launching their new site JVIS decided to localize to Japanese, Chinese, Korean, Russian and Spanish. These are the languages spoken by their larger clients./p pAt that point Jason Marshall contacted a href=http://www.icanlocalize.comus/a about translating JVIS' website. It was already built (as a collection of 23 HTML files), ready to be translated. Our translation service would have produced another 92 static HTML files which JVIS would have uploaded to their server. It was clear that JVIS was going to be adding new content on a regular basis and maintaining it all in several languages without using a content management system would have been a very unwelcome task./p pThe likely possibility of turning a client from being happy to frustrated, due to this manual content management, concerned us very much./p pWe suggested to a href=http://www.jasonmarshall.net/Jason Marshall/a, the web designer who built JVIS website, to first migrate it all to a CMS and only then begin the translation process. The first choice was bDrupal/b, given its powerful multilingual capabilities. bMaintaining a multilingual Drupal site would be much simpler/b, not just for us, but mostly for the client. From the client's point of view, only English texts would need to be managed. Drupal would automatically handle everything else./p pa href=http://drupal.org/node/442712 target=_blankread more/a/p

Read more: http://drupal.org/node/442712