Closed
Bug 867363
Opened 11 years ago
Closed 11 years ago
Update Strings In Creative Brief
Categories
(Websites :: Firefox Flicks, defect)
Websites
Firefox Flicks
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bensternthal, Unassigned)
Details
(Whiteboard: [qa-])
Attachments
(1 file)
5.01 KB,
text/rtf
|
Details |
Received Via Email ================== This year, we need your help to inspire others to Get Mobilized. <br> That means harnessing the power of the Web on mobile devices to discover new content… <br> … exploring how that content connects you to new ideas… <br> … and discovering how those ideas can enrich your life. <br> To that end, we’re asking you to write, produce and edit a video of no more than 60 seconds… <br> … that tells the story of how having access to the Web through a mobile device can change the way you see the world and how you function within it. <br> You don’t have to use a mobile device to make your video. <br> All in 60 seconds or less. <br> Together, we can bring the promise of the Web to the next billion people coming online.
Reporter | ||
Comment 1•11 years ago
|
||
Greg: please advise on the placement of the above strings in this file: https://firefoxflicks.mozilla.org/en-US/strings I am not sure if this is a 100% replacement or if the above strings get interweaved into the existing content.
Flags: needinfo?(gjost)
Comment 2•11 years ago
|
||
It's a mix but since updating the brief is going to be a manual process on my end, I thought we could use a separate string altogether?
Flags: needinfo?(gjost)
Reporter | ||
Comment 3•11 years ago
|
||
The context of the surrounding text is important for localizers. The strings page should match the final text/layout of the creative brief. If you have the EN-US creative brief final, upload as an attachment to this bug and I can make the strings file match.
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
Attaching a text file that shows which strings are staying and which are being replaced with new content. black: string doesn't change red: string removed blue: new string Hope this gives you a better sense of what goes where. I really want to avoid for localizers to have to retranslate strings they already translated for past versions. What is the best way to do that?
Reporter | ||
Comment 6•11 years ago
|
||
In general if a string is exactly the same they won't re-translate. However sometimes because the context changes they do need to re-translate. Txt file (after a glance) looks good.
Reporter | ||
Comment 7•11 years ago
|
||
Gregory - changes in PR please review and let me know if I have missed anything. https://github.com/mozilla/firefox-flicks/pull/208/files
Reporter | ||
Comment 8•11 years ago
|
||
Gregory: Can you review the above changes and let us know if we are good to go. If so we can string merge and get this and all the other updates out to the localizers. Many Thanks!
Flags: needinfo?(gjost)
Comment 9•11 years ago
|
||
This is correct Ben. Quick comment though: lines 20-21 are one slide and same with lines 23-24. This is not a huge issue so we can leave it as if it's too much work to change but it might be better if they were part of the same string.
Flags: needinfo?(gjost)
Comment 10•11 years ago
|
||
Commit pushed to master at https://github.com/mozilla/firefox-flicks https://github.com/mozilla/firefox-flicks/commit/a25247505a63331172b627e0130806b76d171f04 Fix Bug 867363 - update strings for creative brief minor change from Gregory
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•