As part of today’s global economy, business applications are being asked to support users in their native languages. Iron Speed Designer supports developers looking to embrace these international requirements in the software they create. While Iron Speed Designer has no “magic switch” you can throw that generates your application in one language or another, it does support most customizations you would naturally want to make when localizing your application.
|
|
|
Applications built with Iron Speed Designer support local date formats, currency symbols and character sets. |
A variety of factors, settings, and parameters contribute to a localized application:
Culture encoding. Your application has a culture coding that indicates to the .NET Framework how to handle basic properties, like data and time formatting, language, etc.
Page encoding. Iron Speed Designer supports UTF-8 Unicode encoding throughout your application.
Date and time formatting. A variety of date and time formats are used worldwide. Applications built with Iron Speed Designer are built on the .NET Framework, so the date and time field displays and input fields take their cue from the particular culture setting in the Machine.config file or Web.config file.
Number and currency formatting. Some number formats use a decimal point to separate dollars and cents; other formats use commas.
Error text string translation. The error and information text messages in the application classes should be translated to the appropriate language for your application.
One important note: Applications created with earlier versions of Iron Speed Designer before V1.5 can be localized, but only web pages created in V1.5 or later will use the localized strings. This is because the underlying code generated by V1.5 and later makes use of the text string resource files.
Currency Formatting and Validation
Date Formatting and Validation
Error and Validation Message Strings
Enabling Language Support in Microsoft Windows