Ietf-languages Digest, Vol 118, Issue 11

Tue Dec 18 06:30:34 CET 2012

Le 2012-12-18 00:25, ietf-languages-request at alvestrand.no a écrit :
> Send Ietf-languages mailing list submissions to
> 	ietf-languages at alvestrand.no
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.alvestrand.no/mailman/listinfo/ietf-languages
> or, via email, send a message with subject or body 'help' to
> 	ietf-languages-request at alvestrand.no
>
> You can reach the person managing the list at
> 	ietf-languages-owner at alvestrand.no
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ietf-languages digest..."
>
>
> Today's Topics:
>
>     1. Re: Code [zgh] adopted (ISO639-3) (Doug Ewell)
>     2. gender voice variants (Peter Constable)
>     3. pseudo-localization variants (Peter Constable)
>     4. Re: gender voice variants (Phillips, Addison)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 17 Dec 2012 19:41:23 -0700
> From: "Doug Ewell" <doug at ewellic.org>
> To: <ietf-languages at iana.org>
> Cc: Patrick <patrick at hapax.qc.ca>
> Subject: Re: Code [zgh] adopted (ISO639-3)
> Message-ID: <AB639BF84A8B42799A4E3BF2804995E6 at DougEwell>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> 	reply-type=original
>
> Patrick wrote:
>
>>> Doug Ewell scripsit :
>>> This came the day before the end of the comment period for the
>>> 2012 series change requests for 639-3.
>> I'm not too sure why this is important.
> I mentioned it because much is made of the annual ISO 639-3 change
> cycle, and for most requests, if they are not acted upon during the
> current cycle, one must wait another year for the next cycle, and yet
> there are requests such as this one that are processed in between
> cycles.
>
> I have no problem with 'zgh', and I'm glad you were able to get your
> request processed, even if there was some delay. I wonder sometimes if
> this will ever happen for Medieval and Ecclesiastical and Katharevousa
> Greek.
>
> --
> Doug Ewell | Thornton, Colorado, USA
> http://www.ewellic.org | @DougEwell ?
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 18 Dec 2012 03:48:06 +0000
> From: Peter Constable <petercon at microsoft.com>
> To: "ietf-languages at iana.org" <ietf-languages at iana.org>
> Subject: gender voice variants
> Message-ID:
> 	<c8ced7e6d60449f7a6ee4971a391eb1e at BN1PR03MB071.namprd03.prod.outlook.com>
> 	
> Content-Type: text/plain; charset="us-ascii"
>
> I was thinking about this the other day dealing with the male/female voice variants for Nokia Maps. I don't recall that anyone has ever proposed variant subtags for male voice vs. female voice for use on speech assets. (I suppose child voice might be another relevant variant.) Does it seem appropriate to handle these voice distinctions via variant subtags on a language tag?
>
>
>
> Peter
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.alvestrand.no/pipermail/ietf-languages/attachments/20121218/d23fc7b3/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 18 Dec 2012 04:18:45 +0000
> From: Peter Constable <petercon at microsoft.com>
> To: "ietf-languages at iana.org" <ietf-languages at iana.org>
> Subject: pseudo-localization variants
> Message-ID:
> 	<db0e23b3213744a5ac0230dcedacd00f at BN1PR03MB071.namprd03.prod.outlook.com>
> 	
> Content-Type: text/plain; charset="utf-8"
>
> A lot of companies use pseudo-localization methods for testing localizability in which a source string in the development (e.g., in English) is transformed into a different spelling that uses other characters, changes the length and perhaps other things to provide something that can still be read in the same language by the development team / localization engineers but that emulates some of the qualities that might arise when the strings are truly localized. For example, ?Bing App custom protocol? might be pseudo-localized to ?[HoKVu]????? ??? ?????m ??????????? or (for bidi testing) to ????(Bing App custom protocol!)?????.
>
> Within MS, there?s been a bit of up and down history with how pseudo-loc content has been handled. When this was first done, all content got tagged using Windows numeric locale IDs (LCIDs), and there wasn?t one for pseudo, so the LCID for some language that Windows wasn?t localized into was used, which worked until the day came when Windows actually _was_ localized into that language. After some iterations, today a private-use language subtag ?qps? is used. Sadly, none of the complete tags are valid BCP 47 tags, since non-registered variant subtags are used. (Even more sadly, the main one that?s most frequently used wouldn?t even be viable as a variant subtag since it?s only 4 letters.)
>
> That?s made me wonder if it wouldn?t make sense to register one or more variant subtags for pseudo-localized content.
>
>
> Thoughts?
>
>
> Peter
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.alvestrand.no/pipermail/ietf-languages/attachments/20121218/f579180b/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 17 Dec 2012 21:04:07 -0800
> From: "Phillips, Addison" <addison at lab126.com>
> To: Peter Constable <petercon at microsoft.com>
> Cc: "ietf-languages at iana.org" <ietf-languages at iana.org>
> Subject: Re: gender voice variants
> Message-ID: <f3f9432wwhsitwqyntjox0iu.1355807047927 at email.android.com>
> Content-Type: text/plain; charset="utf-8"
>
> It doesn't sound like a valid use to me: it's not a language variation.
>
> I could see it as an additional private use ID or as part of an extension used in a format like SSML. But I have a hard time thinking of it as a language variation. What next? Accent?
>
> Addison
>
> Addison Phillips
> Globalization Architect (Lab126)
> Chair (W3C I18N WG)
>
> Sent from my Kindle Fire HD
>
> Peter Constable <petercon at microsoft.com> wrote:
>
> I was thinking about this the other day dealing with the male/female voice variants for Nokia Maps. I don?t recall that anyone has ever proposed variant subtags for male voice vs. female voice for use on speech assets. (I suppose child voice might be another relevant variant.) Does it seem appropriate to handle these voice distinctions via variant subtags on a language tag?
>
>
>
> Peter
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.alvestrand.no/pipermail/ietf-languages/attachments/20121217/4f560ac7/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages
>
>
> End of Ietf-languages Digest, Vol 118, Issue 11
> ***********************************************
>
>
>
> -----
> Aucun virus trouve dans ce message.
> Analyse effectuee par AVG - www.avg.fr
> Version: 2012.0.2221 / Base de donnees virale: 2637/5466 - Date: 17/12/2012
>
>