public User interface texts generation

Contents [-]

How the system generates the words in the user interface

The content presented by the system can be roughly divided into two types:

user generated content
this a content that the users are submitting to the system after it was installed and launched. It could be text, audio, images and video. This content is not meant to be localized to another languages than the one it was created. This is why changing the language pack of an application, will not alter it in any way.
system generated content
this is a content that was created in the development of the system and was submitted by the developers. It also could be text, audio, images and video, but it was meant to be customized and localized. If you want to customize the colors and the images of the interface, you can do that by applying another user interface pack. If you want to customize the words the system is using in its interface, you can do that by applying another language pack.

For the system to be able to "know" which are the right words to be substituted by the new language pack, it uses a combination of the language tag and a language template. In this way the system does not have in its code the correct words, but only markers formed by this pair.

For example, if you  want the system to generate the word "menu" for, somewhere in the interface, It will not use just "menu" in the code, but #339933;">translate:wfc_menu. So what if you are saying to the system is this:

  • "#339933;">translate: " - this is the system functional tag for dealing with words, which searches for the template key ("wfc_menu") in the installed pack, gets its template_value ("menu") and replaces the whole piece ("#339933;">translate:wfc_menu") with the value. In this way, the user will see only the word "menu" or any other word that corresponds the language template "wfc_menu" in the installed language pack.
  • "wfc_menu" - this is what we call a "template_key". It is the unique index of a word or piece of text in the language pack. The language tag applies these template_key <-> template_value pairs to actually translate the interface on different languages or to customize it with custom words.

How the interface could be switched to a different language?

As described above, the interface should be first prepared to posses the ability to change its language. In all applications developed by WordFrame this ability for language localization will be present.

The language is changed based on application. It could be English for one of the Blogging applications, but German for the other. This is also widely used to make the interface more targeted depending on the focus group of users. For example, in one of the blogging applications the post could be called just "post", for another - "article", for another - "review" and so on.

In general to switch the interface to a different language you need to:

  1. Install the language pack you want to be used (you need to support the target application)
  2. Assign the selected application to use it
  3. and .. that's it.

How to customize only several words on the interface?

If you want to customize only few words, not the entire interface, the smartest thing to do is not to bother preparing and installing a whole new language pack, but use the "Custom snippet & language tags" screen described bellow on this page.

Last edited by nadia on 26 Oct 2010 | Rev. 5 | This page is public | Views: 1
Comments: 0 | Filed under: root | Tags: