From: Bob T. <bo...@el...> - 2002-02-20 19:45:38
|
On 20 Feb 2002 at 14:18, Matthew McNaney wrote: > Why does it matter if static information is served up when the > content is always written in one language anyway? Here are a few advantages: 1. Ability to log severity of error messages 2. Hardcoded statements with hard coded translations are hard to change. If you change one word in the program, for instance, to correct a spelling error, or clarify the message, then all the language files have to be changed. This means that mistakes in messages are less likely to be fixed. 3. If a site operator modifies the programs, you either have to modify the source program, then generate the language version, requiring an extra step, or, if you change the translated version and do a "diff" to the untranslated, your diff is so full of TRANSLATE differences that you can't find see your actual code changes. It would make program updates easier. 4 In the new core, I understand the goal is to have one tree support multiple sites. It wouldn't matter to me for my own uses, but in some uses, it would be necessary. In Quebec, Canada, for instance, I believe French and English are required by law for most public businesses. Well, personally I thought this would be a great benefit, but I won't push it. Happy Coding! -- Bob Treumann, 651-603-1245 Elmwood Solutions Inc. (St. Paul, Minnesota) bo...@el... http://www.elmwood.com ORACLE Business Alliance Program Member |