RE: [Media Capture] Human readable message not localizable? [I18N-ISSUE-465] ( LC-3027)

CC: public-i18n-core

> -----Original Message-----
> From: dom@w3.org [mailto:dom@w3.org]
> Sent: Tuesday, July 07, 2015 6:14 AM
> To: Phillips@jessica.w3.org; Phillips, Addison
> Cc: public-media-capture@w3.org
> Subject: Re: [Media Capture] Human readable message not localizable?
> [I18N-ISSUE-465] ( LC-3027)
> 
>  Dear Phillips, Addison ,
> 
> The Web Real-Time Communications Working Group has reviewed the
> comments you sent [1] on the Last Call Working Draft [2] of the Media
> Capture and Streams published on 14 Apr 2015. Thank you for having taken
> the time to review the document and to send us comments!
> 
> The Working Group's response to your comment is included below, and has
> been implemented in the new version of the document available at:
> http://w3c.github.io/mediacapture-

> main/archives/20150629/getusermedia.html.
> 
> Please review it carefully and let us know by email at public-media-
> capture@w3.org if you agree with it or not before 17 July 2015. In case of
> disagreement, you are requested to provide a specific solution for or a path
> to a consensus with the Working Group. If such a consensus cannot be
> achieved, you will be given the opportunity to raise a formal objection which
> will then be reviewed by the Director during the transition of this document
> to the next stage in the W3C Recommendation Track.
> 
> Thanks,
> 
> For the Web Real-Time Communications Working Group, Dominique
> Hazaël-Massieux Vivien Lacourba W3C Staff Contacts
> 
>  1.
> http://www.w3.org/mid/7C0AF84C6D560544A17DDDEB68A9DFB52EDE0D89

> @ex10-mbx-36009.ant.amazon.com
>  2. http://www.w3.org/TR/2015/WD-mediacapture-streams-20150414/

> 
> 
> =====
> 
> Your comment on message of type DOMString, readonly , nullable:
> > https://www.w3.org/International/track/issues/465

> >
> >
> http://www.w3.org/TR/2015/WD-mediacapture-streams-20150414/#widl-

> MediaStreamError-message
> >
> > The 'message' value of MediaStreamError has no associated language or
> > base direction information. Multiple 'message' values in different
> > languages are not provided for. Since the message is generated by the
> > user-agent, this may already be appropriately localized, but what
> > about remote or hosted cases? And having the language and direction
> > metadata may be useful when presenting the string in JS alerts or in
> > an HTML context.
> >
> > Addison Phillips
> > Globalization Architect (Amazon Lab126) Chair (W3C I18N WG)
> 
> 
> Working Group Resolution (LC-3027):
> As discussed on the list, these error messages are intended for debugging
> and not for display in the user interface; also, should error messages need
> better internationalization support, this should be handled at the EcmaScript
> or WebIDL level, not in this particular specification.
> 
> The Working Group doesn't plan on making change based on this comment.
> 
> ----
>

Received on Tuesday, 7 July 2015 15:04:42 UTC