Blog: Posts from June, 2011

Labels
AJAX(112) App Studio(7) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(183) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Posts from June, 2011
Monday, June 27, 2011PrintSubscribe
Globalization and Localization

Code On Time web application generator creates standard ASP.NET web projects and web sites, which take full advantage of ASP.NET globalization infrastructure. Globalization in ASP.NET has been perfected by Microsoft to allow creation of web applications that work with all cultures and languages. The building blocks are there and our web application generator puts them together to offer a great solution for your globalization and localization needs.

image

Globalization

Code On Time applications offer full support for world cultures, including date and time, calendar, numeric, and currency formats. Your application code may use one culture for the server side business logic and a different culture for presentation.

Globalization settings are configured in the project wizard on the page titled Globalization and Localization. The screen shot below shows this page in a new project.

image

Culture and UI Culture drop down lists are automatically configured to match the locale of your computer. The screen shot above shows both inputs set to en-US, English (United States) .

The selections in these drop downs are the primary culture set of your application where Culture is governing the culture used in the code executed on the server and UI Culture is controlling the user interface culture aspects of the application.

If you are not planning to create applications for other locales then do not make any changes and simply click Next to continue project configuration.

If you are developing an application for a locale that is different then the one selected in Culture and UI Culture then make sure to change the selections accordingly.

Unlimited edition of web application generator allows specifying multiple culture sets.

You can define multiple culture sets by selecting  combinations in Culture / UI Culture drop downs and pressing Add Cultures button.

For example, if you are developing a line-of-business application that is expected to have users primarily in United States then you may anticipate that users from two neighbor countries Canada and Mexico may need to be supported as well. In this age of glo,bal commerce it should not be surprising that the business users of your web application may need to interact with partners from a far away country such as Taiwan.

Given the example above your application must support English, French, Spanish, and Traditional Chinese. The screen shot below shows the configuration of the corresponding supported culture sets.

image

You can also enter the support culture sets directly into the textbox as follows:

en-US, en-US; es-MX, es-MX; en-CA, en-CA; fr-CA, fr-CA; zh-TW, zh-TW;

Multiple culture sets are separated by semicolon or line breaks. Culture is separated from UI Culture by a comma within each culture set definition. If both Culture and UI Culture are the same then enter just one culture. UI Culture may be non-specific and defined by two letters of the language (fr, es, en).

This particular example assumes that users in different locales do not share the server culture.

This is all that is necessary to ensure that your application will correctly present and process date, time, calendars, numbers, and currency values in one or more locales.

Localization

Code On Time web application generator performs automatic localization of all standard application resources in the languages matched to the UI cultures. Our elegant localization system makes supporting multiple localized resources exceptionally simple and accessible.

Localization is one of the most complex aspects of application development. Various text fragments are typically dispersed in static application files such as pages, menus, reports, help system. Text messages are also emitted by business rules to report all sorts of errors and instructions to the end users of a web application.

ASP.NET does provide standard means of externalizing application resources and creating localized versions of each resource file. A developer must maintain all resource files in sync and embed references to specific resources whenever a fragment of text needs to be referenced.  In fact a developer has to translate their entire application in the language of resource IDs that are subsequently translated into actual text written in the natural language. If your application is AJAX-based then you need to employ additional resource DLLs to ensure that localized text resources are available to the client scripts, which makes the localization process even more complex. Resource files in ASP.NET web applications have XML format, which requires users to exercise great care when changing them.

We have decided to eliminate the complexity from this necessity.

Every generated Code On Time application includes several kinds of files commonly found in many hand-coded ASP.NET web applications:

  • Ajax Client Library resources (*.js files)
  • Data Controller Descriptors (*.xml files)
  • Web Pages (*.aspx files)
  • User Controls (*.ascx files)
  • Site Maps (*.sitemap files) B
  • Core Library and Business Logic (*.cs or*.vb files)

We use a refreshingly simple and consistent method of localizing the application source code. If you open the generated application source code in Visual Studio or Windows Explorer then you will find a collection of text files that include the names of UI cultures supported in your web application.

The screen shot shows the partial contents of the root folder of a generated application that supports cultures listed in the discussion of a globalization example above.

image

The screen shot shows ClientLibrary.*.txt, Resources.*.txt, and Web.Sitemap.*.txt groups of text files.

The first group defines the localized Client Library resources for all supported locales.

The second group defines localized resources used in the business rules and core library of the generated application.

The third group defines a collection of localized resources found in the Web.Sitemap, the file that describes the navigation hierarchy of the application.

You will find a few other clusters of localized resources if you browse the contents of the project. Notice that all of these clusters are associated with a specific static source file of your project much like Web.Sitemap and its satellite resources.

Let’s take a look inside.

Here is the first three lines from ClientLibrary.en-US.txt.

^About^About^About^

^ActionBarActionsHeaderText^Actions^ActionBarActionsHeaderText^

^ActionBarCancelActionHeaderText^Cancel^ActionBarCancelActionHeaderText^

Next example shows the first three lines from ClientLibrary.fr-CA.txt.

^About^À propos^About^

^ActionBarActionsHeaderText^Actions^ActionBarActionsHeaderText^

^ActionBarCancelActionHeaderText^Annuler^ActionBarCancelActionHeaderText^

This snippet shows the first three lines from ClientLibrary.zh-TW.txt.

^About^關於^About^

^ActionBarActionsHeaderText^動作^ActionBarActionsHeaderText^

^ActionBarCancelActionHeaderText^取消^ActionBarCancelActionHeaderText^

You have probably noticed the pattern that includes localization brackets on both sides of a localized resource. A localization bracket must start and end with “^” and may contain any combination of alphanumeric characters, such as ^About^, ^Label1^, and ^23^. We call the combination of matching brackets and text between them a localization token.

Here is an example of localization tokens SiteHome, HomePath, and HomeDesc found in Web.Sitemap.

  <siteMapNode url="~/Default.aspx" title="^SiteHome^Home^SiteHome^" description="">
    <siteMapNode title="^HomePath^Home^HomePath^" 
description="^HomeDesc^Application home page^HomeDesc^"
url="~/Pages/Home.aspx" />

Sample code using localization token RecordChangedByAnotherUser is shown next. Method Replace of class Localizer automatically adds “^” to the localization token name and wraps it around the text fragment. This class is the core class of your application. You may find yourself using Localizer.Replace if you need to write a custom business logic in a multi-lingual web application.

if (result.RowsAffected == 0)
{
    result.RowNotFound = true;
    result.Errors.Add(Localizer.Replace("RecordChangedByAnotherUser", 
"The record has been changed by another user.")); }

You can see that the localization token name is present along with the default text fragment in both use cases. This makes it much easier to understand the intended result. Your web application will remove the localization token at runtime and try to find the resource associated with the token in a file matched to the current web request UI culture. If the localized resource is found then it is used in place of the default value. If the exact match of a specific culture such as “fr-CA” is not found then the localizer will try to see if there is a file that matches a non-specific culture “fr”.

All resource text fragments of the core server and client libraries are written in English. Your can replace them if you change the localization files with the corresponding culture. For example, if your culture is en-US then change the files that end with *.en-US.txt to replace the default English fragments. Do not change the corresponding source code files directly.

If you change the value between localization brackets and save the file then you have effectively changed the localized text representation of the corresponding physical resource of your web application. Simply run your application and observe your changes to resource files in action.

If you application is based on a Visual Studio solution file (if you are developing a Web App Factory, Azure Factory, or SharePoint Factory project) then you will need to compile your application.

Files ClientLibrary.*.txt are not a part of your application. The web application generator will use the contents of these files to customize the JavaScript library of your application. If you change any definitions in ClientLibrary.*.txt file set then make sure to re-generate your project for the changes to take effect. Make sure to hit Refresh button of your browser to ensure that the most current version of localized resources is loaded in the web browser window.

Other localization file sets found in your project must be deployed along with the application.

Localization files found in the class libraries of your project (applies to Web App Factory, Azure Factory, SharePoint Factory) will have the culture component in the file name using “_” instead of “-“.

Here is a brief description of all standard localization files sets.

File Set Folder Description
ClientLibrary.*.txt ~/ JavaScript Client Library resources.
Resources.*.txt ~/ Resources used in the core application classes and business rules of application.
Web.Sitemap.*.txt ~/ Text and description of navigation nodes presented in application menu.
aspnet_Membership.xml.*.txt ~/Controllers Membership manager resources.
aspnet_Roles.xml.*.txt ~/Controllers Role manager resources.
TableOfContents.ascx.*.txt ~/Controls Text fragments used in the standard table of contents that presents the site map as a tree.
Welcome.ascx.*.txt ~/Controls Text fragments used in the welcome message.
Home.aspx.*.txt ~/Pages Resources definitions found in the home page.
Membership.aspx.*.txt ~/Pages Resource definitions found in the membership manager page.
Template.xslt.*.txt ~/Reports Resource definitions used in RDLC report template.

Modified localization files are preserved by web application generator. If a new localization token is introduced in the core library and you have an existing application that does not have such a token then the code generator will insert the token in the file with value equal to the default text fragment from the code generation library.

Multiple Cultures / Languages

Your application may support any number of user interface languages with the same code base. The application framework offers easy-to-use localization of static resources and simple API to render localized messages produced by your custom business rules.  We have shown examples of localized static resources and business rules in the previous topic.

This capability is available in the Unlimited edition of Code On Time.

Automatic Translation

Wrap localization brackets around any text. Web application code generator will perform full translation in all languages supported by your application.

For example, the screen shot below shows the list of fields in Customers data controller. You can see that the field labels in the third column from the right have been changed to include localization brackets. Numerical and named tokens such as ^ContName^ and ^3^ are being used for localization.

image

We have also changed various text properties of Customers page in designer.

image

The following versions of Customers screen are presented if we generate our application and select languages corresponding to fr-CA and zh-TW cultures.

image

image

If you inspect the generated application then you will notice the following new culture sets that were created by Code On Time web application generator.

Localization files for ~/Pages/Customers.aspx

image
Localization files for ~/Controllers/Customers.xml

image

Feel free to open any of these text files to refine the localized text fragments. Generated applications monitor localization files and will start using the fresh content when you save the changes.

Language Detection

Code On Time web applications will automatically detect the supported culture. If the client browser culture is supported by your  app then the appropriate localized resources are utilized to render the pages without any user involvement.

Web browsers send language preferences to web servers with each request. Culture manager of the generated web application will automatically match a supported culture set with the languages accepted by the user’s browser. If a match is found then the culture set is automatically selected.

If the matching culture is not found then the application will use the default culture set of your application that was selected on Globalization and Localization page of project wizard.

Language Selector

Membership bar offers a list of languages supported in your application with native names presented to application users. Language selection is automatically memorized and maintained with a sliding expiration.

Language selector complements automatic language detection.

We Need Your Help

Automatic translation of localized resources is performed via Google Translate. The result of translation may not meet your expectations and we apologize for that.

We need your help with creating high quality localized standard resources. If you do make changes to any of the localized files listed below then please contribute your translations to benefit the developer community. You will find additional instructions in ClientLibrary.*.txt files in the root of your applications.

We are looking for assistance with the following files:

  • ClientLibrary.*.txt
  • Resources.*.txt
  • Web.Sitemap.*.txt
  • aspnet_Membership.xml.*.txt
  • aspnet_Roles.xml.*.txt
  • TableOfContents.ascx.*.txt
  • Welcome.ascx.*.txt
  • Home.aspx.*.txt
  • Membership.aspx.*.txt
  • Template.xslt.*.txt

Your contribution will be included in the general distribution of the code generation library. We will post the names of contributors on our blog with a link to contributor’s website if requested.

Monday, June 27, 2011PrintSubscribe
Chinese Culture Processing

Code On Time web application generator now correctly performs automatic translation of all English resources to Chinese (Simplified) or Chinese (Traditional) when required. This change effects zh-CHS, zh-CHT, zh-CN, zh-HK, zh-MO, zh-SG, and zh-TW user interface cultures of generated web applications.

The following sets of culture-specific resources are now included with the code generation library: de, es, fr, hi, it, ja-JP, pt, pt-PT, zh-CHS, and zh-CHT.

If your culture is not listed then the web application code generator will automatically translate the baseline set of resources in English to your locale with the help of Google Translate. Translation is performed only one time per project. Subsequent code generation does not require translation.

Note that translations are of “automated translation” quality.

Saturday, June 25, 2011PrintSubscribe
Localization, Globalization, In-Page History

This a significant update to Code On Time web application generator and core library of generated applications. The summary of changes and enhancements is listed below.

Few users have reported a problem with automatic update installation. If the you experiencing errors while trying to upgrade then simply uninstall Code On Time and download a fresh copy at http://codeontime.com/download.aspx.

The update includes a brand new localization framework. All resources were externalized. There is a single file that can be changed to modify ALL of the client library text strings.

File ClientLibrary.*.txt (for example, ClientLibrary.en-US.txt or ClientLibrary.pt-BR.txt) will be created in the root of the project when you generate your application with the updated version of the code generator. Unlimited edition users can have multiple ClientLibrary.*.txt files matched to their selected cultures if more than one culture is supported.

If you change resource tokens in the file and re-generate the project one more time then the client library will use the content supplied by you. The ClientLibrary.*.txt file is not required at runtime.

There will also be additional resource files that are matched to resources such Web.Sitemap (for example, Web.Sitemap.fr-CA.txt) or data controllers descriptors (for example, ~/Controllers/aspnet_Memberhship.it-IT.txt). Changes to the files will be reflected at runtime. These files are a part of your application.

The web application generator will automatically produce localization files and perform actual translation using Google Translate if you apply a certain syntax to the text labels.

The localization and globalization tutorial will be available.

Fixes and improvements in this release:

  • Localization of both Web App Factory and Web Site Factory has been completed.
  • The entire client library now supports a mechanism to translate resources in a language of your choice.
  • In-Page History is now implemented in the Client Library. Previous implementation has stored user filters in the Session object on the server. The session state was restored whenever the data had to be presented. This was creating a somewhat undesirable user experience effect and significantly increased the size of the user session data. The new implementation will save history in the page and will restore the history only if you return to the page via Back button of your browser.
  • Container menus will now remember the selected tab. The new implementation of the in-page history will restore the selected tabs and selected row in Grid and Data Sheet views.
  • Field-level errors are now displayed in pop out boxes one at a time. This is probably the most visible change from the end user perspective. You can see the new style of field-level error message if you leave a mandatory field empty in a form and try saving it.
  • The bug preventing setting focus on a field in a Data Sheet view has been fixed.
  • Automatic localization of localized resources via Google Translate is now supported in all editions of the code generator.
  • Two new classes Localizer and CultureManager are now a part of the core framework of generated applications.
  • Membership bar will now display a language selector if multiple UI cultures are supported in your application. Multiple cultures are supported in Unlimited edition only.
  • Dynamic reports are using the current UI culture and display currency, numbers, and dates as is required by locale.
  • Adaptive filters have been changed to supported “typed” filter values. Previous implementation has been relying on simple string conversions between the client and the server. “Typed” values eliminate all sorts of filtering problems that were encountered with some locales.
  • Designer will open all objects in “edit” mode when an object is selected from a grid view. This should speed up and simplify project modifications.
  • Page containers show tabs with linked data views and controls when selected in Designer.
  • Numeric values will not wrap when displayed in Grid and Data Sheet views.
  • Modal forms will maintain the same width if user navigates between records using navigation arrows.
  • Interface System.Web.SessionState.IRequiresSessionState is implemented in all generic handlers to support ASP.NET session. This will ensure that you can access session data in business rules during import, export, and blob processing.
  • Membership bar replaces the browser URL to prevent the home page with login prompt from being displayed when user clicks the Back button in a browser. This only affects applications that do not rely on a dedicated login page.
  • The 'About'  box header text on pages has been placed in resources to support globalization.
  • BusinessRules class implements Localize(token,text) method to simplify localization of messages sent to the client from business rules classes.
  • MembershipBusinessRules class is using the new Localize method to display system messages.
  • Grid views will remember the last view type (Data Sheet or Grid) selected by end user and restore the view type when user returns back to the page via browse Back button.
  • Help system has been upgraded to include configuration instructions. It has been enhanced to match the web application theme and display a relevant customization instruction when a user selects Help link on the membership bar.
  • System messages by blob handler, controller, and annotation plug-in are now localized via global Resources.*.txt file.
  • Component DataViewExtender now supports method AssignStartupFilter. This method allows setting up an initial filter values using custom code. We recommend placing a custom user control on a page in designer and writing the logic assigning the initial filter in the code-behind file of the user control.
  • Import processor is not using the thread pool anymore. This will eliminate the bug related to unavailability of HttpContext during the export process. Context is now available since the execution of the import process is not asynchronous anymore. We will revisit this later to see if asynchronous processing can be accomplished via other means.
  • Added support for missing handlers to allow blob, reports, etc. with IIS / IIS Express and .NET 3.5 web apps. This was typically resulting in BLOB images not displayed when application is executed.
  • Sandbox app in Web App Factory solutions will now have the same base page YourNamespace.Web.PageBase to support globalization and localization.

Coming next:

  • Azure Factory project is ready to go. We wanted to implement a complete localization framework prior to rolling this out. The plan is to roll Azure Factory out over the next weekend. The feature will be available to Premium edition users.
  • Partial implementation of the Tree view has been released in this update. You can give it a try if you change the type of grid view to “Tree” in Designer and add a self-referring data field to this view. We are hoping to complete this data presentation style in the release. The feature will be available to Premium edition users.
  • Custom Membership and Role providers. We are planning to include this feature in Unlimited edition.