Closed
Bug 1028429
Opened 10 years ago
Closed 10 years ago
[marketing][screenshot][sr-Latn]: screenshot updated for 1.3 campaign
Categories
(Mozilla Localizations :: sr / Serbian, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: CocoMo, Assigned: tlow87)
References
Details
Hi Team,
This is an update from the 1.1 screenshot you two completed last year. The update utilized most of the screenshots (at least with same strings). Thanks to flod, we are putting the strings in the system, so we can retain all the work for future updates.
Reference material:
1). Screenshots 1.1 (sr-Latn): https://mozilla.app.box.com/files/0/f/1252198296/Serbian_%28Latin%29_PNG
2). Screenshots 1.3 (en): https://mozilla.box.com/s/g5b7mjx198ay2q2kcka6
3). String source 1.3 (en): https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxos-marketing/en-US/screenshots.lang
4). Dashboard: http://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=9&file=screenshots.lang
One of the tricky parts in strings we need is the contact list: fake names of equal number of males and females; last names in consecutive order (such as f, g, h), and half of them have some kind of profession/company names associated with them.
This is a new process for the graphic agency. During review and implementation phase, your "revision" needs to be specific, so the graphic person knows which strings to look for (no color code like we did in spreadsheet). When all are finalized, make sure the "corrected" strings are in SVN so it is the source of truth, not the bug.
Thank you,
Peiying
Comment 1•10 years ago
|
||
I wil work with Aleksandra Uzelac on this and I notes that files are unavailable. Please check them again or send them to us on some other way.
Reporter | ||
Comment 2•10 years ago
|
||
I just added you two. Let me know if you can NOT access to the "en" folder.
Comment 3•10 years ago
|
||
(In reply to Peiying Mo [:CocoMo] from comment #0)
> One of the tricky parts in strings we need is the contact list: fake names
> of equal number of males and females; last names in consecutive order (such
> as f, g, h), and half of them have some kind of profession/company names
> associated with them.
I need help regarding this. I'm not sure how I should add the fake names and professions in the lang file. Should I separate them with a comma? For example, in screen 13: Travis Gray and bellow T. Gray Photography.
Should I type the name and profession together, separated by comma, like this: Travis Gray, T. Gray Photography?
Just to make it clear, I'll be adding custom names, not the ones that are in screenshots. Travis Gray is just a example.
Flags: needinfo?(pmo)
Reporter | ||
Comment 4•10 years ago
|
||
Hi Aleksandra,
If it is common practice to sort name by last, then you would say Gray, Travis/Photography (or Gray, Travis/T. Gray Photography. You can also indicate gender by adding (m) or (f) at the end of the name. The graphic person would know which one to use with an image.
If the common practice is to sort name by first, then you would say Travis Gray/T. Gray Photography.
Whichever the case, make sure the sorting letters are consecutive (m, n, o, or f, g, h). They must be fake. You can think of people you know and switch them up a bit. Common names are the best to go with.
Here are some examples from Spanish (sort by last name) and Portuguese (sort by first name) we did earlier that may help you: https://docs.google.com/a/mozilla.com/spreadsheets/d/1--aIDyyKhxPER6uniRaNgcixVUq_H6FwOLRADRWBLwg/edit#gid=0
Comment 5•10 years ago
|
||
Screenshots.lang has been translated and uploaded:
http://viewvc.svn.mozilla.org/vc/projects/l10n-misc/trunk/firefoxos-marketing/sr/screenshots.lang?r1=129876&r2=129875&pathrev=129876
Reporter | ||
Comment 6•10 years ago
|
||
Thank you for such quick turnaround.
Flags: needinfo?(pmo) → needinfo?
Reporter | ||
Comment 7•10 years ago
|
||
Hi Tannie, Serbian is ready to go.
Assignee: marko.andrejic93 → tlow87
Flags: needinfo?
Assignee | ||
Comment 8•10 years ago
|
||
Aleksandra, here are the SR screens for review: https://mozilla.box.com/s/uaylm8wwau5mpmvzvcaw
Notes
-----
12-EverythingMe_Cafe: truncated 'Klubovi ljubitelja knjiga' to 'Klubovi ljubitelja...'
18-DataUsage: I noticed you using '25. maj' in the Email screen, but 'maj 1' on the usage screen. Checking consistency. Also, what is the proper translation for 'bytes', and abbreviations for 'MB, GB, and KB'?
19,20-Lockscreen: similar question about date consistency
Thanks!
Comment 9•10 years ago
|
||
(In reply to Tannie Low from comment #8)
> 12-EverythingMe_Cafe: truncated 'Klubovi ljubitelja knjiga' to 'Klubovi
> ljubitelja...'
Change it to: "Ljubitelji knjiga"
> 18-DataUsage: I noticed you using '25. maj' in the Email screen, but 'maj 1'
> on the usage screen. Checking consistency. Also, what is the proper
> translation for 'bytes', and abbreviations for 'MB, GB, and KB'?
For the date part: It can be changed to "1. maj" (a dot after the date) but it's not a problem if it stays.
For bytes is "bajta", for MB and other it should stay as it is.
> 19,20-Lockscreen: similar question about date consistency
On my Firefox OS v1.4, the date is as it is on the picture, with no dot after the date (that's how our localizers translated it and I thought it should stay the same, even though the correct format should be "26. maj"). Ether way, it's not a problem if it stays.
Comment 10•10 years ago
|
||
Everything else looks ok.
Assignee | ||
Comment 11•10 years ago
|
||
Aleksandra,
Screens 12 & 18 have been updated: https://mozilla.box.com/s/uaylm8wwau5mpmvzvcaw
Once you approve those revisions, and give them another look over, I'll go ahead and begin exporting the hi-res files. Thanks!!
Comment 12•10 years ago
|
||
Everything looks ok. It's good to go :)
Reporter | ||
Comment 13•10 years ago
|
||
Yay!! Thanks Aleksandra and Tannie to get this done so quickly!
Tannie, please post hi-res URL here as soon as they are complete.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 14•10 years ago
|
||
Hi-res PNGs: https://mozilla.box.com/s/5i633mfq9i7rx0ie4y4i
You need to log in
before you can comment on or make changes to this bug.
Description
•