Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n-ISSUE-464: 'label' needs direction and language metadata #78

Open
r12a opened this issue Mar 16, 2016 · 3 comments
Open

i18n-ISSUE-464: 'label' needs direction and language metadata #78

r12a opened this issue Mar 16, 2016 · 3 comments
Labels
needs-resolution i18n expects this item to be resolved to their satisfaction. s:mediacapture-streams https://w3c.github.io/mediacapture-main/ t:bidi_strings 3.5 Handling base direction for strings t:lang_strings 2.4 Identifying the language of strings wg:webrtc https://www.w3.org/groups/wg/webrtc

Comments

@r12a
Copy link
Contributor

r12a commented Mar 16, 2016

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ w3c/mediacapture-main#665

(Moving from http://www.w3.org/Mail/flatten/index?subject=i18n-ISSUE-464&list=public-media-capture )


Raised by:Addison Phillips
Opened on:2015-04-24

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

The 'label' value is described as follows:

User Agents MAY label audio and video sources (e.g., "Internal microphone" or "External USB Webcam"). The MediaStreamTrack.label attribute MUST return the label of the object's corresponding source, if any. If the corresponding source has or had no label, the attribute MUST instead return the empty string.

Since the value is intended to contain natural language text, probably for consumption/display to the end-user, maybe it should be possible to determine or set the language (@lang) and base direction (@dir) of the text. This will allow the text to be displayed properly in different contexts.

In addition, it may be useful to allow multiple labels in different languages (although generally the source's label is applied by the user's user-agent, and so will be appropriately localized??)

@r12a r12a added the s:mediacapture-streams https://w3c.github.io/mediacapture-main/ label Mar 16, 2016
@r12a r12a added the needs-resolution i18n expects this item to be resolved to their satisfaction. label Nov 16, 2018
@xfq
Copy link
Member

xfq commented Mar 9, 2020

@w3cbot w3cbot added the close? The related issue was closed by the Group but open here label Oct 2, 2020
@aphillips aphillips removed the close? The related issue was closed by the Group but open here label Sep 30, 2021
@w3cbot w3cbot added the close? The related issue was closed by the Group but open here label Oct 1, 2021
@r12a r12a added t:bidi_strings 3.5 Handling base direction for strings t:lang_strings 2.4 Identifying the language of strings labels Jul 21, 2022
@aphillips aphillips added the needs-attention The i18n WG should urgently review the status of this item. label Aug 31, 2023
@aphillips
Copy link
Contributor

I believe we may still be in a not satisfied state here.

@w3cbot w3cbot added the wg:webrtc https://www.w3.org/groups/wg/webrtc label Feb 9, 2024
@aphillips aphillips removed the needs-attention The i18n WG should urgently review the status of this item. label May 23, 2024
@aphillips
Copy link
Contributor

Discussed in 2024-05-24 call https://www.w3.org/2024/05/23-i18n-irc#T14-27-14

@aphillips aphillips removed the close? The related issue was closed by the Group but open here label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-resolution i18n expects this item to be resolved to their satisfaction. s:mediacapture-streams https://w3c.github.io/mediacapture-main/ t:bidi_strings 3.5 Handling base direction for strings t:lang_strings 2.4 Identifying the language of strings wg:webrtc https://www.w3.org/groups/wg/webrtc
Projects
None yet
Development

No branches or pull requests

4 participants