Inconsistent strings for premium/protected content |
|||||||
Issue descriptionfbeaufort started a thread about a confusing translation in the protected media content UX: https://groups.google.com/a/chromium.org/forum/#!topic/security-enamel/CeouiyHpO8Y Here is the French translation bug: https://gloc-qm.appspot.com/issues/protected-media-prompt-is-unclear-8c4105df/ The English strings are also inconsistent. We say "premium" in the permission request: <ph name="URL">$1<ex>https://www.youtube.com</ex></ph> wants to uniquely identify your device to play premium content. But "protected" in the Chrome Settings screen (see screenshot).
,
Mar 30 2017
,
Mar 30 2017
We talked about this when we add that UI on desktop chrome and at that time we thought "content" isn't obvious to a lot of users and "protected media" might be a better choice. But I searched again and it seems "protected content" is actually used more often than "protected media" [1]. Note that "Premium content" is actually used more often, but it's mostly in the context of gaming [2]. Adobe Flash also uses "Protected Content" [3]. With that, I feel "protected content" is the right choice. But I'd like to hear the opinions from PM and UX. [1] https://trends.google.com/trends/explore?q=%22protected%20content%22,%22protected%20media%22,%22premium%20content%22,%22premium%20media%22 [2] http://store.thesims3.com/category.html?categoryId=13062&action=premiumContentView [3] https://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager08.html
,
Mar 31 2017
We may want to replace all occurrences of "premium content" by "protected content" in chromium source code: https://cs.chromium.org/search/?q=%22premium+content%22+package:%5Echromium$&type=cs
,
Apr 19 2017
Re #4: I think the change makes sense. But we need UX approval. ericde / mlamouri: How do we get UX involved here?
,
Apr 19 2017
+Hotlist-Media-UX is going to put this in our bugs requiring UX attention. Though, I'm afraid this might be hard for our Media UX person to talk as there is a lot of background they do not have. xhwang@, do you know who was involved in the previous discussions on the UX side?
,
Apr 19 2017
s/to talk/to look at/ (not sure how I ended up writing this)
,
Apr 19 2017
,
Apr 25 2017
+ Shimi, who might be able to advise on the process for fixing confusing translations?
,
Apr 25 2017
I do not recommend that we replace all occurrences of "premium content" with "protected content." In IDS_PROTECTED_MEDIA_IDENTIFIER_INFOBAR_QUESTION, "<SITE> wants to uniquely identify your device to play premium content.", I agree that this should be changed to "protected" to be technically correct. The fix has already been made in French, but we should fix the EN source. In IDS_DEL_MEDIA_LICENSES_COUNTER_GENERAL_COMMENT and IDS_DEL_MEDIA_LICENSES_COUNTER_SITE_COMMENT, "You may lose access to premium content" string in the Clear Browsing Data dialog, this string is intended to warn users of the implication of deleting media licenses. I didn't write this string, but I believe the use of "premium" here was deliberate and is valid. xhwang@, I'm fine with continuing to use "content" instead of "media," but should we then change "Media licenses" in CBD to "Content licenses" to maintain consistency with the content setting language? Or just leave it as is? I also found one instance of "protected media" that should be changed to "protected content": IDS_PLATFORM_VERIFICATION_DIALOG_HEADLINE, "DOMAIN wants your device's identity to be verified, by Google, to determine eligibility for enhanced playback of protected media." These strings & recommendations are documented for easier reference: https://docs.google.com/document/d/1DacqTZ_xIXmxeJ68GJaQ7eHKegk9nQcu2iOhhOMkpII/edit?hl=en
,
Apr 26 2017
srahim: Thanks for the thorough investigation! I agree with most of your suggestions, except the "Media Licenses" one which I am not sure. I definitely saw cases of using "content licenses" in this context, but also there are users who has no idea about what "content licenses" are, especially since we also have "content settings". So that might cause a bit confusion. That being said, I don't have strong opinion on this.
,
Apr 26 2017
Thanks, xhwang! Since this bug is about "protected" v. "premium", let's see if there is additional feedback on those strings first. We can decide the "media license" v. "content license" question separately.
,
Apr 27 2017
Thanks! With that, I'll approve https://codereview.chromium.org/2791433002. I'll add srahim@ to that CL as well.
,
May 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a0996c57176ab23a9f4aac30bc9fadc94de696b9 commit a0996c57176ab23a9f4aac30bc9fadc94de696b9 Author: palmer <palmer@chromium.org> Date: Thu May 04 02:10:03 2017 Use "protected" instead of "premium" for media content. So that the UI strings are consistent across Chrome. BUG= 706871 Review-Url: https://codereview.chromium.org/2791433002 Cr-Commit-Position: refs/heads/master@{#469246} [modify] https://crrev.com/a0996c57176ab23a9f4aac30bc9fadc94de696b9/chrome/app/chromeos_strings.grdp [modify] https://crrev.com/a0996c57176ab23a9f4aac30bc9fadc94de696b9/chrome/app/generated_resources.grd
,
May 8 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by palmer@chromium.org
, Mar 30 2017