🚀 go-pugleaf

>I hope that everyone will share their metrics with insoft-l as time goes
>on.  In other words, exactly how long did it take you to internationalize
>your application?  Today, I can't give you a percentage, but it's greater
>than zero.

0% is a correct answer for us.  The application was not internationalized.
It was implemented with I18n techniques as a required coding practice (no
different than writing comments, avoiding globals, etc.).  Thus when it
came time to do the localizations, there were very few bugs preventing
localization and the nature of the bugs was minor.  Thus the total time
spent fixing internationalization problems is on the order of 2 days per
year.  In integer math that is 0%.  In any case, our experience is that
writing an application that is ready for localization (ie: is international)
is no more time consuming than not.  The main difference is training new
people to the methodology.  We would use message tables or UIL or some other
equivalent even for applications that aren't going to be translated outside of
US english.

Dick