Hi Steve,
I have thought through this before and here are the issues/ideas I found:
1. Product Cart has three main “languages” files, one for the main site, one for the one-page checkout and one for shipping. The main file is included on every page of the front end of the site. It includes 100s of text labels in English. In order to use a different language, someone (the merchant) would need to duplicate all of those labels, change the variable names from English to the new language and then translate all of the labels to that language. All of the labels for all languages would need to be included in this same file which would get quite large. Fortunately it is processed on the server so it is pretty quick but the file will increase in size with each new language. I would recommend customizing this as well so that the dictionary only loads the elements for the language specified.
2. The template (header/footer) files will need to NOT use any language specific text, i.e. all text such as navigation links, titles, section headings, etc. would need to be added to the languages file.
3. PC uses multiple button images/icons throughout the site. These are only defined in one place, i.e. using one language. Different sets of images would need to be loaded/displayed based on the selected language.
4. The email content sent to customers when orders are placed is only defined for one language. There would need to be a way to edit those emails for each language and the email sending routines would need to select the correct language.
5. All categories and products are defined in only one language. Our initial thoughts would be: Create top level categories for each required language. The subcategories would be duplicated under each language where the merchant can enter different translation of the categories for each language. Each product would need to be duplicated for each language and linked to the correct subcategory for that language.
The product categories navigation on the site would need to be customized to only show product subcategories under the main category for the selected language.
6. Content Pages: Merchant would need to create a language specific content page for each page of content. We'd need to designate which language the page links to and then only show content pages for the selected language in the navigation.
7. Biggest issues are how to handle multiple currency formats, weights (lbs vs. kilo), etc. by country.
Hope that sheds some more light on the subject.
As Greg mentioned, in the end, multiple sites is probably the quickest and least expensive route especially when considering upgrades.
------------- NetProfits Internet Consulting
Certified ProductCart Developer
http://www.nicwebdesign.com" rel="nofollow - Our Site
|