[Marketing][screenshots][zh-TW]: Fx for iOS 3.0 submission



2 years ago
2 years ago


(Reporter: petercpg, Assigned: tlow87)


Firefox Tracking Flags

(Not tracked)


Hi Ty, Peiying, 

Thanks for making screenshots again for zh-TW. There are some redundant spaces in the iPad images, please make following fixes:

- FFx-iOS_zh-TW_iPad-*_Search.png
Replace space between 速 and 聰 with "、"

- FFx-iOS_zh-TW_iPad-*_Sync.png
Remove space between 取 and 開, before 書 (if there is one), 籤 and 與

- FFx-iOS_zh-TW_iPad-*_Tabs.png
Remove space between 的 and 瀏

- FFx-iOS_zh-TW_iPad-*_Users.png
Remove space between 入 and 數

- Font
The glyph of font used to make these screenshots is not what we use in zh-tw. Please use Adobe Source Han Sans TC or the same variant of Google's Noto Sans, 
(Story in Bug 1207275)


Comment 1

2 years ago
Thank you for this feedback, Peter! 

Tannie, let me know if you have any questions on these changes.
Assignee: tflanagan → tlow87
Flags: needinfo?(tlow87)

Comment 2

2 years ago
New PNGs ready for review in the same folder: https://drive.google.com/folderview?id=0B3AF_F4vcknOVEN2ZThIeTlfWFk&usp=sharing
Flags: needinfo?(tlow87) → needinfo?(petercpg)
Hi Tannie, text are good now, but the font is still incorrect.
Flags: needinfo?(petercpg) → needinfo?(tlow87)

Comment 4

2 years ago
I'm on it! Is this for all the zh-TW and zh-CN PNGs (not just iPad)?

Comment 5

2 years ago
I'm using the Source Han Sans Pro TW that we used in the last round, but it doesn't seem to be applying to every character. Some revert to the Adobe font. I'll re-download the latest release (https://github.com/adobe-fonts/source-han-sans/releases/tag/1.004R) and give it another try.

Comment 6

2 years ago
zh-TW and zh-CN PNGs ready for review: https://drive.google.com/folderview?id=0B3AF_F4vcknOTEVZWmkzRlR2R2M&usp=sharing
Flags: needinfo?(tlow87) → needinfo?(petercpg)
It's all correct for zh-TW, Thanks Tannie!
Last Resolved: 2 years ago
Flags: needinfo?(petercpg)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.