Re: 4.2 intro and 4.4.1

Hi,

Good example. Note that translating Gozen and Gogo to AM and PM works out ok,
but the 0:00 needs to convert to 12:00. Same confusion apparently exists in
English, see excerpts from Heritage dictionary below.

tex

> Time       : To do		Western/English
> ---------- : -----------------------
> GOZEN 8:00 : Breakfast    8:00 A.M.
> GOGO  0:00 : Lunch       12:00PM
> GOGO  7:00 : Dinner		7:00 PM
> GOZEN 0:00 : Go to bed	12:00AM


http://dictionary.reference.com/search?q=pm

P.M. also p.m. or P.M.
abbr. post meridiem.
Usage Note: By definition, 12 A.M. denotes midnight, and 12 P.M. denotes noon,
but there is sufficient confusion over the meanings of A.M. and P.M. when the
hour is 12 to make it advisable to use 12 noon and 12 midnight where clarity is
required.

http://dictionary.reference.com/search?q=am

also a.m. or A.M.ante meridiem. 
Usage Note: By definition, 12 A.M. denotes midnight, and 12 P.M. denotes noon,
but there is sufficient confusion over these uses to make it advisable to use
12 noon and 12 midnight where clarity is required. 

Source: The American Heritage® Dictionary of the English Language, Fourth
Edition
Copyright © 2000 by Houghton Mifflin Company.
Published by Houghton Mifflin Company. All rights reserved. 



Takao Suzuki wrote:
> 
> Here is my attempt to fill 4.2 intro section and 4.4.1 Pandora's box.
> 
> -takao
> 
> 4.2 Locale/Language Dependency in Message Exchange Patterns
> 
> When exchanging a message, the requester and service that the requester
> accesses may have different default locales and language preferences. In
> addition, there may be more than one service involved in the message
> exchange.  And there may be different requester, who consumes the
> message, who may expect different locale and language.
> 
> Message exchange in components with different language and/or locales
> may result a failure or unexpected result.  This section describes
> various message exchange patterns that need consideration or that have
> potential failure scenarios.
> 
> 4.4.1 Using non-internationalized Data Structures
> 
> A data structure may be provided without international considerations.
> This may happen, for instance, when a service was originally designed
> and targeted for a specific local market and later adopted to a global
> Web service.
> 
> This is an example of my daily activity provided in Japanese 12 hour
> time scheme.
> 
> Example: My schedule
> 
> Time       : To do
> ---------- : -----------------------
> GOZEN 8:00 : Breakfast
> GOGO  0:00 : Lunch
> GOGO  7:00 : Dinner
> GOZEN 0:00 : Go to bed
> 
> GOZEN means "before noon", and generally corresponds to AM. GOGO means
> "after noon", and generally corresponds to PM. The problem is GOGO 0:00
> is noon rather than 0:00 AM, and GOZEN 0:00 is midnight rather than 0:00
> PM.  This is confusing and conversion to internationally known time
> format may fail.
> 
> Thank you

-- 
-------------------------------------------------------------
Tex Texin   cell: +1 781 789 1898   mailto:Tex@XenCraft.com
Xen Master                          http://www.i18nGuy.com
                         
XenCraft		            http://www.XenCraft.com
Making e-Business Work Around the World
-------------------------------------------------------------

Received on Tuesday, 30 March 2004 23:48:52 UTC