posted 05-01-99 03:49 PM ET
A number of issues contributed to it being late. I guess you missed the other posts where I spelled it out. One part of the problem was competing with other projects for EA testing and translation resources. It's a huge company, with dozens of products, all with unique and pressing schedules. As you might imagine, patches don't often get priority over deadlined retail releases.
Another problem was the multiphase testing of the product, between 4 different locations. Once OSI signed off on the patch, it then went to EAHQ in Redwood City. After a stint there, it heads over to EAUK for the final okay. Any problems encountered can often causes a new patch to be generated, and the entire process began anew. This describes the current situation with the French patch, though we were able to bypass the first two testing phases for the re-submition.
Coupled with the last point, if a language specific bug is encountered, often we need additional translation (shortening strings to fit on buttons, for instance).
I hope that explains just some of the potential issues related to localized patches. Because of the ill-will many customers generated because of the these unavoidable, though unfortunate, delays. We are seriously considering holding all patches from release until they are all complete for v4.0. What's your take on that? A good idea. Keep in mind though, that would signifigantly delay the v4.0 release, since the current languages that would require a patch are English, French, German, Spanish, and Italian.
jkm
firaxis games