[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltru] xml:lang syntax



Trying to solve the kinds of problems xml:lang="mul-en-fr" is trying to solve has nothing to do, IMO, with the issues we're trying to sort out to complete 4646bis, and belongs entirely on the side of the consuming application of 4646bis, not in 4646 itself. I think we could end that discussion.


My $.02.

Peter



> -----Original Message-----
> From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On Behalf Of
> Leif Halvard Silli
> Sent: Thursday, May 08, 2008 2:07 AM
> To: Andrew Cunningham
> Cc: LTRU Working Group
> Subject: Re: [Ltru] xml:lang syntax
>
> Andrew Cunningham 2008-05-08 10.04:
> > 2008/5/8 Leif Halvard Silli <lhs at malform.no>:
> >
> > >  This means that we can say xml:lang="mul" and encompass all the
> > >  langugeas of the world. But not any two or more languages. With
> > >  xml:lang="mul-en-fr" one coud be more spesific.
> >
>
> > Doing something like xml:lang="mul-en-fr" would not be a good way to
> > go. The xml:lang attribute would indicate the language of the
> contents
> > of an element and should be a single value. Adding multiple vlaues
> > would affect inheritance of language values. It would effect
> > processing data and displaying data.
> >
>
> Rethinking: Perhaps it is not advicable on the xml:lang tag, which only
> is inside the root element - if I remember. But the very thing, to be
> able to specify mul-en-fr on other elements than the root element,
> seems
> meaningful to me.
>
> Does that sound better?
>
> But otherwise, even for xml:lang, there is no principle diff between
> xml:lang="mul" - which I guess isn't forbidded - and xml:lang="mul-en-
> fr".
> --
> leif halvard silli
> _______________________________________________
> Ltru mailing list
> Ltru at ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www.ietf.org/mailman/listinfo/ltru



Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.