[OWASP-ESAPI] Internationalization

[Jim Manico]

I've been talking with Pawan off-line about ESAPI internationalization,
here are my thoughts:

1) We need a basic Internationalization interface for ESAPI that all
other ESAPI libraries will use when displaying user data
2) We need to add a "locale" attribute to the ESAPI User object.
3) Functions in the Internationalization interface supported should include
    a) convert a string to a specific locale  (this one only will be
used mostly by the other ESAPI classes)
    b) edit a certain string/locale combinatio
    c) delete a certain string/locale combination
    d) list all supported locales
4) The interface should be able support several different kinds of persistence engines - resource bundles or a database.

Here, let me just bust out some psuedocode...

Interface Internationalizer {
    //sourceData is a token to represent a label on a GUI in the apps base language, usually US english
    String result function i(String sourceData, Locale l);
    //handles add or edit events
    void editTranslation(String sourceData, String editData, Locale locale);
    void deleteTranslation(String sourceData, Locale locale);
    //delete all translations for a specific token 
    void deleteTranslation(String sourceData);
    //delete all translations for a specific locale
    void deleteTranslation(Locale locale);
    List<Locale> getLocales();
    List<String> getTokens(Locale locale);      
}

Thoughts?
- Jim
 
-- 
Jim Manico, Senior Application Security Engineer
jim.manico at aspectsecurity.com
(301) 604-4882 (work)
(808) 652-3805 (cell)

Aspect Security(tm)
Securing your applications at the source
http://www.aspectsecurity.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-esapi/attachments/20090215/6a0a2ecd/attachment.html