Message-Id: <6.1.2.0.2.20050406151907.035821d0@mail.jefsey.com>
Date: Wed, 06 Apr 2005 15:27:29 +0200
To: "L.Gillam" <L.Gillam@surrey.ac.uk>, ltru <ltru@ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Ltru] Re: Registry in record-jar format - smart matching?
In-Reply-To: <4A7C6FA2AB31194E80E13FE585F6A2121A5939@EVS-EC1-NODE1.surre
	y.ac.uk>
References: <4A7C6FA2AB31194E80E13FE585F6A2121A5939@EVS-EC1-NODE1.surrey.ac.uk>
Mime-Version: 1.0
Cc: 
Precedence: list
Content-Type: multipart/mixed; boundary="===============1095854910=="
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

--===============1095854910==
Content-Type: multipart/alternative;
	boundary="=====================_10721106==.ALT"

--=====================_10721106==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 14:21 06/04/2005, L.Gillam wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>         boundary="----_=_NextPart_001_01C53AA3.212C7525"
>
>Defaults + fallback = ?
>
>If "en" defaults to en-Latn, does en-Cyrl falls back to en and default to 
>en-Latn. Is it better to receive en-Latn rather than "nothing" in response 
>to en-Cyrl? What if more than one script is implicated by the 2 letter 
>language code, there is a default, but the fallback should produce all 
>available?
>
>What do people think is the best result from this combination?

The question seems precisely that: what "people think". Because there can 
be different types of defaults depending of the types of people (educated 
or not, bi-scriptural,.. this is in part alluded to in the  APMD Draft) or 
inter-application or man/machine. For example if the concerned page has a 
lot of visuals and language is only a help or  is full text, this makes a 
real difference.

This means that the same page may be better read by two different people 
with two different defaults. This kind of issue is precisely the purpose of 
the "context" we work on - which may include languages, locales, scripts, 
terminology etc. at low load (preloaded at boot in using the CRCD I 
documented). An XML page should be able to document its context tag and its 
elements to overide its langtag default. This corresponds to the mention of 
"preferences" in the Charter.

jfc


--=====================_10721106==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
At 14:21 06/04/2005, L.Gillam wrote:<br>
<blockquote type=cite class=cite cite="">Content-class:
urn:content-classes:message<br>
Content-Type: multipart/alternative;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>boundary=&quot;----_=_NextPart_001_01C53AA3.212C7525&quot;<br><br>
<font size=2>Defaults + fallback = ?<br>
</font><br>
<font size=2>If &quot;en&quot; defaults to en-Latn, does en-Cyrl falls
back to en and default to</font> <font size=2>en-Latn. Is it better to
receive en-Latn rather than &quot;nothing&quot; in response to en-Cyrl?
What if more than one script is implicated by the 2 letter language code,
there is a default, but the fallback should produce all available? <br>
</font><br>
<font size=2>What do people think is the best result from this
combination?</font></blockquote><br>
The question seems precisely that: what &quot;people think&quot;. Because
there can be different types of defaults depending of the types of people
(educated or not, bi-scriptural,.. this is in part alluded to in
the&nbsp; APMD Draft) or inter-application or man/machine. For example if
the concerned page has a lot of visuals and language is only a help
or&nbsp; is full text, this makes a real difference.<br><br>
This means that the same page may be better read by two different people
with two different defaults. This kind of issue is precisely the purpose
of the &quot;context&quot; we work on - which may include languages,
locales, scripts, terminology etc. at low load (preloaded at boot in
using the CRCD I documented). An XML page should be able to document its
context tag and its elements to overide its langtag default. This
corresponds to the mention of &quot;preferences&quot; in the
Charter.<br><br>
jfc<br><br>
</body>
</html>

--=====================_10721106==.ALT--



--===============1095854910==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru

--===============1095854910==--