W3C home > Mailing lists > Public > www-international@w3.org > April to June 2008

Re: [Comment on WS-I18N WD]

From: Dan Chiba <dan.chiba@oracle.com>
Date: Mon, 16 Jun 2008 12:27:55 -0700
Message-ID: <4856BEBB.5080408@oracle.com>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
CC: www-international@w3.org

IMHO searching contents in a specific language is a related but separate 
issue. A search engine may return results in language(s) indicated in 
the WS-I18N structure, but as Felix points out, a user may be interested 
in contents in language(s) other than the UI language.

A search engine whose help is provided in English and German is indeed a 
good use case for the requirement to identify the UI language 
independently from locale. For example, a French speaking user in 
Switzerland would want German translation and Switzerland locale 
conventions for datetime and number formatting. Then #1 locale="fr-CH" 
and #3 language="de".

Support for non-translation locale sensitive operations such as datetime 
and number formatting is available for most common locales and usually 
the system can serve the user in his or her most preferred locale. On 
the other hand, it must select the UI language from among the available 
languages, so the selected preferred language is often different from 
the preferred locale.


Frank Ellermann wrote:
> Felix Sasaki wrote:
>> I'm using a search engine with an English or German user 
>> interface, but I want to get results from the area of Japan.
> For one of the two search engines you have mentioned the
> hl=de parameter picks the UI (~ "help language: German").
> To get results limited to JP you can add &cr=countryJP
> to your query URL.  More radically you can add site:jp
> to the query string, but this eliminates JP results in
> other TLDs.  "Local search" is no I18N issue, or is it?
>  Frank
Received on Monday, 16 June 2008 19:29:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:29 UTC