- From: Peter Saint-Andre via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Sep 2018 15:43:46 +0000
- To: public-i18n-archive@w3.org
stpeter has just created a new issue for https://github.com/w3c/i18n-activity: == highly detailed text in video content == MediaStreamTrack Content Hints, §2.2 Video Content Hints https://www.w3.org/TR/2018/WD-mst-content-hint-20180703/#video-content-hints > The track should be treated as if video details are extra important, and that significant sharp edges and areas of consistent color can occur frequently. This is generally applicable to presentations or web pages with text content. This setting would normally optimize for detail in the resulting individual frames rather than smooth playback, and may take advantage of encoder tools that optimize for text rendering. Artefacts from quantization or downscaling that make small text or line art unintelligible should be avoided. Different written scripts might require different levels of detail (e.g., so that small features such as aspiration marks can be distinguished), and even a video content hint with a value of "text" might not be adequate for some scripts. Perhaps a "health warning" that a value of "text" provides no guarantee that textual features can be distinguished might be helpful. --- **WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered. **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:** § link_to_issue_raised Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/599 using your GitHub account
Received on Thursday, 27 September 2018 15:43:48 UTC