Change 'Cast to' term to 'Send to ' in-product

VERIFIED FIXED in Firefox 34

Status

()

VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: krudnitski, Assigned: mfinkle)

Tracking

(Blocks: 1 bug, {late-l10n})

34 Branch
Firefox 35
ARM
Android
late-l10n
Points:
---

Firefox Tracking Flags

(firefox34 verified, firefox35 verified, fennec34+)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

4 years ago
As discussed over email, Fx 33 will have the 'Cast to ' terminology, but this should be changed to 'Send to ' for Fx 34
(Reporter)

Comment 1

4 years ago
Sorry for the spam, but I meant to file this after Arcadio's final input and discussion with Matej. Adding Arcadio to comment.
Flags: needinfo?(alainez)
Created attachment 8474798 [details] [diff] [review]
casting-strings v0.1

WIP
Assignee: nobody → mark.finkle
FYI, I changed "Cast to Device" to "Send to Device" and "Cast to Screen" to "Send to Device"

Comment 4

4 years ago
(In reply to Mark Finkle (:mfinkle) from comment #3)
> FYI, I changed "Cast to Device" to "Send to Device" and "Cast to Screen" to
> "Send to Device"

Are those purposely both "device" now? Should the second one still be "screen"?
(In reply to Matej Novak [:matej] from comment #4)
> (In reply to Mark Finkle (:mfinkle) from comment #3)
> > FYI, I changed "Cast to Device" to "Send to Device" and "Cast to Screen" to
> > "Send to Device"
> 
> Are those purposely both "device" now? Should the second one still be
> "screen"?

No. For some reason I diverged the strings very early and never took the time to fix them. I think Google originally used "Screen" but moved to "Device". I am happy with "Device" used everywhere.
(Assignee)

Updated

4 years ago
tracking-fennec: ? → 34+
Comment on attachment 8474798 [details] [diff] [review]
casting-strings v0.1

I guess we need this landed soon to get in Fx34
Attachment #8474798 - Flags: review?(wjohnston)
Comment on attachment 8474798 [details] [diff] [review]
casting-strings v0.1

Review of attachment 8474798 [details] [diff] [review]:
-----------------------------------------------------------------

::: mobile/android/chrome/content/CastingApps.js
@@ +428,5 @@
>      // 2. The video is allowed to be cast and is currently playing
>      // Both states have the same action: Show the cast page action
>      if (aVideo.mozIsCasting) {
>        this.pageAction.id = PageActions.add({
> +        title: Strings.browser.GetStringFromName("contextmenu.sendToDevice"),

Hmm.. This string is actually kinda wrong. i.e. Shouldn't it read "Stop sending to device" or something?

@@ +435,5 @@
>          important: true
>        });
>      } else if (aVideo.mozAllowCasting) {
>        this.pageAction.id = PageActions.add({
> +        title: Strings.browser.GetStringFromName("contextmenu.sendToDevice"),

Are you ok with page actions reusing the context menu string? I think I can live with it. Maybe worth a note for localizers or a rename to "menu.sendToDevice"

::: mobile/android/locales/en-US/chrome/browser.properties
@@ +206,5 @@
>  # Text Selection
>  selectionHelper.textCopied=Text copied to clipboard
>  
>  # Casting
> +casting.sendToDevice=Send to Device

This key is a little less descriptive for localizers about where it will appear.
Attachment #8474798 - Flags: review?(wjohnston) → review-
(In reply to Wesley Johnston (:wesj) from comment #7)
> Comment on attachment 8474798 [details] [diff] [review]

> ::: mobile/android/chrome/content/CastingApps.js

> >        this.pageAction.id = PageActions.add({
> > +        title: Strings.browser.GetStringFromName("contextmenu.sendToDevice"),
> 
> Hmm.. This string is actually kinda wrong. i.e. Shouldn't it read "Stop
> sending to device" or something?

No. The code will open the casting prompt again, allowing you to send the video to a different device. If we wanted to add a "This Device" to the list, like some Google Chromecast enabled apps do, we could add that to a new bug.

> @@ +435,5 @@
> >          important: true
> >        });
> >      } else if (aVideo.mozAllowCasting) {
> >        this.pageAction.id = PageActions.add({
> > +        title: Strings.browser.GetStringFromName("contextmenu.sendToDevice"),
> 
> Are you ok with page actions reusing the context menu string? I think I can
> live with it. Maybe worth a note for localizers or a rename to
> "menu.sendToDevice"

I'm fine with it until we decide to change the string

> ::: mobile/android/locales/en-US/chrome/browser.properties

> >  # Casting
> > +casting.sendToDevice=Send to Device
> 
> This key is a little less descriptive for localizers about where it will
> appear.

I can add a localization note
Created attachment 8481356 [details] [diff] [review]
casting-strings v0.2

This adds the localization comments and also adds a "contentDescription" (and related changes) in the Java side.
Attachment #8474798 - Attachment is obsolete: true
Attachment #8481356 - Flags: review?(wjohnston)
Flags: needinfo?(alainez)
Heads up to L10N that this patch will likely be landing in Aurora very soon after the merge. We'll try to get the patch landed ASAP. PR blog posts are going out referencing the new strings so it's important to get this into Fx34.
Flags: needinfo?(wjohnston)
Keywords: late-l10n
Comment on attachment 8481356 [details] [diff] [review]
casting-strings v0.2

Review of attachment 8481356 [details] [diff] [review]:
-----------------------------------------------------------------

::: mobile/android/locales/en-US/chrome/browser.properties
@@ +387,5 @@
>  # LOCALIZATION NOTE (nativeWindow.deprecated):
>  # This string is shown in the console when someone uses deprecated NativeWindow apis.
>  # %1$S=name of the api that's deprecated, %2$S=New API to use. This may be a url to
>  # a file they should import or the name of an api.
> +nativeWindow.deprecated=%S is deprecated. Please use %S instead

See bug 1054177
Side note: I've never seen late-l10n used on Gecko, at least on the rapid release cycle, not sure how helpful it is.
Attachment #8481356 - Flags: review?(wjohnston) → review+
https://hg.mozilla.org/integration/fx-team/rev/e53a41405553

I am also pushing to aurora because we need the strings ASAP
Flags: needinfo?(wjohnston)
(Assignee)

Updated

4 years ago
status-firefox34: --- → affected
status-firefox35: --- → affected
(In reply to Francesco Lodolo [:flod] (offline from Aug 31 to Sep 7) from comment #11)

> ::: mobile/android/locales/en-US/chrome/browser.properties
> @@ +387,5 @@
> >  # LOCALIZATION NOTE (nativeWindow.deprecated):
> >  # This string is shown in the console when someone uses deprecated NativeWindow apis.
> >  # %1$S=name of the api that's deprecated, %2$S=New API to use. This may be a url to
> >  # a file they should import or the name of an api.
> > +nativeWindow.deprecated=%S is deprecated. Please use %S instead
> 
> See bug 1054177

Right. I didn't change the line, just added a newline at end of file (or my editor did)

Pushed to aurora:
https://hg.mozilla.org/releases/mozilla-aurora/rev/e279f845b3d4
status-firefox34: affected → fixed
https://hg.mozilla.org/mozilla-central/rev/e53a41405553
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35

Comment 16

4 years ago
Verified as fixed in build 34.0a2 (2014-09-05);
Device: Google Nexus 7 (Android 4.4.4).
status-firefox34: fixed → verified

Comment 17

4 years ago
Verified as fixed in build 35.0a1 (2014-09-05);
Device: Google Nexus 7 (Android 4.4.4).
Status: RESOLVED → VERIFIED
status-firefox35: affected → verified
You need to log in before you can comment on or make changes to this bug.