RFC 6497 on BCP 47 Extension T - Transformed Content

Mark Davis ☕ mark at macchiato.com
Thu Feb 23 20:37:28 CET 2012


Thanks!

------------------------------
Mark <https://plus.google.com/114199149796022210033>
*
*
*— Il meglio è l’inimico del bene —*
**



On Wed, Feb 22, 2012 at 22:10, "Martin J. Dürst" <duerst at it.aoyama.ac.jp>wrote:

> Congratulations!     Martin.
>
> -------- Original Message --------
> Subject: RFC 6497 on BCP 47 Extension T - Transformed Content
> Date: Wed, 22 Feb 2012 16:56:32 -0800 (PST)
> From: rfc-editor at rfc-editor.org
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> CC: rfc-editor at rfc-editor.org
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 6497
>
>        Title:      BCP 47 Extension T -
>                    Transformed Content
>        Author:     M. Davis, A. Phillips,
>                    Y. Umaoka, C. Falk
>        Status:     Informational
>        Stream:     IETF
>        Date:       February 2012
>        Mailbox:    mark at macchiato.com,
>                    addison at lab126.com,
>                    yoshito_umaoka at us.ibm.com,
>                    court at infiauto.com
>        Pages:      15
>        Characters: 32915
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-davis-t-langtag-ext-07.**txt
>
>        URL:        http://www.rfc-editor.org/rfc/**rfc6497.txt<http://www.rfc-editor.org/rfc/rfc6497.txt>
>
> This document specifies an Extension to BCP 47 that provides subtags
> for specifying the source language or script of transformed content,
> including content that has been transliterated, transcribed, or
> translated, or in some other way influenced by the source.  It also
> provides for additional information used for identification.  This
> document is not an Internet Standards Track specification; it is
> published for informational purposes.
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/**listinfo/ietf-announce<http://www.ietf.org/mailman/listinfo/ietf-announce>
>  http://mailman.rfc-editor.org/**mailman/listinfo/rfc-dist<http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>
>
> For searching the RFC series, see http://www.rfc-editor.org/**
> rfcsearch.html <http://www.rfc-editor.org/rfcsearch.html>.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.**html<http://www.rfc-editor.org/rfc.html>
> .
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> ______________________________**_________________
> IETF-Announce mailing list
> IETF-Announce at ietf.org
> https://www.ietf.org/mailman/**listinfo/ietf-announce<https://www.ietf.org/mailman/listinfo/ietf-announce>
>
> ______________________________**_________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/**mailman/listinfo/ietf-**languages<http://www.alvestrand.no/mailman/listinfo/ietf-languages>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/ietf-languages/attachments/20120223/6bb7ae3d/attachment.html>


More information about the Ietf-languages mailing list