Examples of hirondelle.web4j.ui.translate.Translator

hirondelle.web4j.ui.translate.Translator
avapractices.com/Topic208.cjp">avoid ResourceBundle.
Guidance For Implementing With A Database
Example of a web application with the following particular requirements (see the example application for further illustration):
- English is the base development language, used by the programmers and development team
- the user interface needs to be in both English and French
- in source code, the programmers use both regular text snippets in user-presentable English, and (occasionally) 'coder keys', according to the needs of each particular case
Here is a style of ResultSet that can be used to implement this interface :

BaseText Locale Translation

Fish And Chips en Fish And Chips

Fish And Chips fr Poisson et Frites

delete en delete

delete fr supprimer

add.edit.button en Add/Edit

add.edit.button fr Ajouter/Changer

Only the last two rows use a "coder key". The BaseText column holds either the coder key, or the user-presentable English. The BaseText is the lookup key. The fact that there is repetition of data between the BaseText and English columns is not a real duplication problem, since this is a ResultSet, not a table - the underlying tables will not have such repetition (if designed properly, of course).
For example, such a ResultSet can be constructed from three underlying tables - BaseText, Locale, and Translation. Translation is a cross-reference table, with foreign keys to both BaseText and Locale. When such a scheme is normalized, it will have no repeated data. (In underlying queries, however, the base language will be necessarily treated differently than the other languages.)
Upon startup, the tables are read, the above ResultSet is created and stored in a private static Map, represented schematically as Map[BaseText, Map[Locale, Translation]]. When a translation is required, this Map is used as an in-memory lookup table. This avoids repeated fetching from the database of trivial data that rarely changes.
Note on Thread Safety
In the suggested implementation style, the private static Map that stores translation data is static, and thus shared by multiple threads. Implementations are free to implement any desired policy regarding thread safety, from relaxed to strict. A relaxed implementation might completely ignore the possibility of a mistaken read/write, since no writes are expected in production, or simply because the consequences are usually trivial. A strict implementation would take the opposite approach, and demand that the private static Map be used in an fully thread-safe manner.

BaseText	Locale	Translation
Fish And Chips	en	Fish And Chips
Fish And Chips	fr	Poisson et Frites
delete	en	delete
delete	fr	supprimer
add.edit.button	en	Add/Edit
add.edit.button	fr	Ajouter/Changer

   The <tt>aLocale</tt> parameter is always required, even though there are cases when it 
   is not actually used to render the result. 
  */
  public String getMessage(Locale aLocale, TimeZone aTimeZone){
    String result = null;
    Translator translator = BuildImpl.forTranslator();
    Formats formats = new Formats(aLocale, aTimeZone);
    if( fParams.isEmpty() ){
      result = translator.get(fText, aLocale);
    }
    else {
      String localizedPattern = translator.get(fText, aLocale);
      List<String> formattedParams = new ArrayList<String>();
      for (Object param : fParams){
        if ( param instanceof RequestParameter ){
          RequestParameter reqParam = (RequestParameter)param;
          String translatedParamName = translator.get(reqParam.getName(), aLocale); 
          formattedParams.add( translatedParamName ); 
        }
        else {
          //this will escape any special HTML chars in params :
          formattedParams.add( formats.objectToTextForReport(param).toString() );

View Full Code Here

    else if(fDateFormat != null && fDateFormatKey == null){
      adjustForTimeZone(fDateFormat, timeZone);
      result = fDateFormat.format(fDate);
    }
    else if(fDateFormat == null && fDateFormatKey != null){
      Translator translator = BuildImpl.forTranslator();
      String localPattern = translator.get(fDateFormatKey, locale);
      DateFormat localDateFormat = new SimpleDateFormat(localPattern, locale);
      adjustForTimeZone(localDateFormat, timeZone);
      result = localDateFormat.format(fDate);
    }
    else {

View Full Code Here

    }
    else if(fFormat != null && fFormatKey == null){
      result = fDateTime.format(fFormat, getLocale());
    }
    else if(fFormat == null && fFormatKey != null){
      Translator translator = BuildImpl.forTranslator();
      String localPattern = translator.get(fFormatKey, locale);
      result = fDateTime.format(localPattern, locale);
    }
    return result;
  }

View Full Code Here

TOP

Related Classes of hirondelle.web4j.ui.translate.Translator

hirondelle.web4j.model.AppResponseMessage

hirondelle.web4j.ui.tag.ShowDate

hirondelle.web4j.ui.tag.ShowDateTime

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.