On Dec 10, 2010, at 11:17 AM, [email protected] wrote:
> Does the Dabo framework include integrated support for localized
> display and conversion of numeric, currency, date, time, datetime
> data? By conversion, I mean the ability to format content for
> presentation in a specific locale and the ability to parse
> free-form input for a specific data type and convert this data to
> a native python data type.
>
> I assume these features would be implemented via either Python's
> locale module or the 3rd party Babel module.
I would assume that the wxPython controls would respect the locale
settings, but to be honest, I'm a typical American who never strays far from
ASCII text and US conventions, so I can't say for sure how well this works. I
rely on the non-American users to point out where Dabo doesn't work correctly.
> I searched the Dabo wiki and found the following page which
> describes localization from a text perspective via the gettext
> module. This page does not discuss the topic above.
> http://wiki.dabodev.com/Internationalization
Internationalization != localization. I've renamed the page to
Localization.
To be localized, all that's required is that there are translations for
the locale's language, and that the code is written to localize all displayed
text. To be internationalized, you need to support a variety of display issues,
such as right-to-left text input and control layout; icons that make sense in
different countries. It's a much more complex topic that is focused on user
interface even more than on translations.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
