02-15-2008 12:14 AM
02-15-2008 12:25 PM
02-15-2008 12:50 PM
02-15-2008 01:13 PM
02-15-2008 01:29 PM
02-15-2008 01:46 PM
02-16-2008 01:40 PM
Ah yes, convert his current French db to English to be used by ACT! for Web... then back to French when the product is available... exactly.
Just a lang file with all the text for localization? I only wish it were that easy! ;-) ACT! has so many disparate resources in so many different formats (Windows Forms, database, 3rd party controls, installers, etc. etc.) that a simple text file for localization is simply not possible. In fact, to try and do something like that would slow ACT! down considerably.
However I do agree with your sentiment about US developers and their tendencies to eschew localization. ACT! does have examples of this. And the guys in Dublin probably are not ACT! experts as they were hired to localize an array of products across Sage. Not to mention that the business is pretty young and the people are still relatively new to Sage.
As for currency, it wouldn't be hard to let you choose on db creation but that wouldn't help collaboration/sync of the data, and I imagine it would generate more support calls and angry customers wanting to merge.
You're right about registry keys (for the most part) and database field names, they are not intended to be localized. Things like that are defects just like any other product defect.
02-19-2008 04:54 AM
02-20-2008 04:34 PM