As I see it, there are several reasons to keep locale. None are related to computer processing, but rather Library Science. One can strike a happy medium though with RFC3066. This is a "language in locale" hybrid - en-US (english in US), ap-MX (apache in Mexico) and so forth. While there is quite a bit of locale style associated with numbers and dates, it is a fair assumption that an author or small group of authors will use some *consistant* style, and translations can be treated as semi-new documents for bibliographic purposes.
http://www.loc.gov/standards/mods/mods-outline.html#language http://dtd.nlm.nih.gov/tag-library/2.2/index.html http://www.diglib.org/preserve/hadtdfs.pdf And besides, I'm soooooo sick of renting video's at Blockbuster (by mistake) in languages I don't speak. This is my revenge. --Gannon --- David Wilson <[EMAIL PROTECTED]> wrote: > On Sun, 28 Jan 2007, Bruce D'Arcus wrote: > > > So translating: > > > > locale -- not sure why we need this? > I am not sure either. Locale information is generally needed only if > the text > is NOT encoded in unicode. In the case where you have a 8bit > character codes > and need the locale to determine the font mapping. I do not think > Writer > would be preserving text this any way - text imported / pasted into a > Writer > document would be converted into the document wide encoding. ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
