Re: [Ltru] Macrolanguage usage

["Phillips, Addison" <[e-mail]>]

Here's the 14 -> 14b diff:

  http://tinyurl.com/5fuw3j

Here's the 14a -> 14b diff:

  http://tinyurl.com/5tshfa

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of
> Phillips, Addison
> Sent: Friday, May 16, 2008 12:36 PM
> To: Randy Presuhn; LTRU Working Group
> Subject: Re: [Ltru] Macrolanguage usage
>
> Hmm... that's a good bit of text.
>
> I incorporated it and did some more editing to cut down the extraneous
> text, incorporate some of Mark/Peter's text, etc. and posted the result
> as editor copy "b" here:
>
>   http://www.inter-locale.com/ID/editor/draft-ietf-ltru-4646bis-
> 14b.html#macrolanguages
>   http://www.inter-locale.com/ID/editor/draft-ietf-ltru-4646bis-14b.txt
>
> Comments?
>
> Addison
>
> Addison Phillips
> Globalization Architect -- Lab126
>
> Internationalization is not a feature.
> It is an architecture.
>
>
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]] On Behalf
> Of
> > Randy Presuhn
> > Sent: Friday, May 16, 2008 12:04 PM
> > To: LTRU Working Group
> > Subject: Re: [Ltru] Macrolanguage usage
> >
> > Hi -
> >
> > As a technical contributor...
> >
> > > From: "Mark Davis" <[e-mail]>
> > > To: "Doug Ewell" <[e-mail]>
> > > Cc: "LTRU Working Group" <[e-mail]>
> > > Sent: Friday, May 16, 2008 11:08 AM
> > > Subject: Re: [Ltru] Macrolanguage usage
> > ...
> > > The only thing that the text is saying is that when there is a
> > predominant
> > > language, for backwards compatibility -- AND with some careful
> > caveats --
> > > the above is broadened. This is *not* with respect to
> permissibility,
> > but
> > > with respect to recommended practice.
> > >
> > >    - It is *permissible* to tag Mandarin text with "und" or "zh" or
> > "cmn".
> > >       - It is a *good idea* to tag/lookup with "cmn"*, except that
> > for
> > >       backwards compatibility, "zh" may be better for many
> > implementations.*
> > >    - It is *permissible* to tag Standard Arabic text with "und" or
> > "ar" or
> > >    "arb".
> > >       - It is a *good idea* to tag/lookup with "arb"*, except that
> > for
> > >       backwards compatibility, "ar" may be better for many
> > implementations.*
> > >
> > > That lets people like Google, which has a very serious and
> important
> > issue
> > > with backwards compatibility, support the vast amount of
> > Mandarin/Arabic/...
> > > that is tagged with "zh", and continue to tag Mandarin content with
> > "zh". It
> > > also lets people like Shawn's group at Microsoft, having no
> backwards
> > > compatibility issues with "cmn" and "zh", to shift over immediately.
> > >
> > > It is also orthogonal to the recommendation for non-predominant
> > encompassed
> > > languages, where we would tag with the more specific tags: "yue",
> > > "yue-Hant-HK", "yue-Hant-US", "abh-AF", and so on, once they are
> > available.
> > ...
> >
> > I'd re-frame it in slightly different terms, as an example of the
> "tag
> > wisely"
> > principle, rather than as anything that might be understood as a
> > recommendation.
> > "For some applications, it is possible that there will be cases where
> > it could
> > be advantageous to deliberately use a tag which is imprecise.  For
> > example,
> > due to the peculiar situation of written Chinese, an application with
> > large
> > quantities of legacy textual data already tagged with 'zh' might
> > countinue
> > to use this over-broad tag even for new data which would more
> precisely
> > be
> > tagged with 'cmn'."
> >
> > Randy
> >
> >
> > _______________________________________________
> > Ltru mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/ltru
> _______________________________________________
> Ltru mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ltru
_______________________________________________
Ltru mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ltru