[Design] Expando Date/Time fields
mimi at osafoundation.org
Wed Jan 11 15:16:59 PST 2006
Actually if you think about it, providing a flexible, modular
framework that allows for culture-specific designs is the most
"internationalizable" thing any piece of software can provide.
On Jan 11, 2006, at 3:08 PM, Alec Flett wrote:
> Mimi Yin wrote:
>> Yeah well there's a difference between English-only modules in the
>> final product and English-only modules for design
>> experimentation._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> I totally agree with this and I think that it also applies to data
> input. While we don't want to just throw out i18n goals, I think
> there is real value both in providing language-specific display and
> input. If that starts with English, so be it. My hope would be that
> if we provide something that works very well in English, and fall
> back to something more generic for other locales, then there will
> be an incentive for translators to contribute back locale-specific
> input/display to improve parity with the English version of Chandler.
> Put another way, if we're already going to force all languages to
> input a very fixed time format like "hh::mm am/pm" why not ALSO
> allow an extended syntax in English?
> If we can find a way to make this system pluggable (and I think
> smart localizers will have to help us there) then we can allow
> people to drop-in their own localized engine to interpret "Hoy a
> las diez"
> If anything, this will spur innovation for open-source date/time-
> entry parsing.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Design" mailing list
More information about the Design