![]() ![]() > As I said above, I know very little about how localized builds are I think the concern is that there are other locales that could be affected by this (at least I am concerned) but I'll let Axel answer. How could Jonathan's patch possibly effect these localizations? But I *really* don't understand what you're saying > I'm by no means a build system expert, especially wrt to doing > But otherwise I think it's fine as it stands, and I don't understand > OS X 10.6 (the earliest version we still support). > is the naming scheme used by Safari and Chrome going back at least to > named "zh_TW.lproj", not "zh-TW.lproj". > This is wrong as it stands - the zh-TW package's lproj file should be > Generate zh-TW.lproj instead of zh.lproj (In reply to Steven Michaud from comment #27) Name the zh.lproj file for the zh_TW localization correctly - we need Zh_CN.lproj (at least for some purposes - for example the language That the OS interprets the filename zh.lproj as synonymous with Have caused trouble for the two Chinese locales (zh_CN and zh_TW) But I do know (from this bug) that it seems *not* to I don't know whether this incorrect naming has caused trouble for Firefox, however, has long (and incorrectly) used just theįirst part of the name (e.g. zh_CN and zh_TW), *both* parts of its name should be If a given localization has more than one Long had seperate distros for each localization, each of whichĬontains a single, appropriately named *.lproj file. Zh_TW.lproj in their Contents/Resources/ directory. So Safari and Chrome have both a zh_CN.lproj and a Safari and Chrome have long had all language support packaged into a Here's my current understanding of this bug, and what we need to do to > I could speculate on this better if someone could explain what's "update_packaging" command to work correctly. But just looking at the code, it seems that en.lproj needs toīe temporarily renamed as per the destination locale for the > Technically, I wonder why the changes in l10n.mk would beĪs I said above, I know very little about how localized builds areĭone. I'm by no means a build system expert, especially wrt to doing Probably visually less obvious, but I'd expect > I'd be surprised if this wouldn't affect our Spanish localizations, OS X 10.6 (the earliest version we still support).īut otherwise I think it's fine as it stands, and I don't understand Is the naming scheme used by Safari and Chrome going back at least to This is wrong as it stands - the zh-TW package's lproj file should be It seems the key to reproduce is you need a Mac in zh-TW locale, with zh-TW build of Firefox.Ĭomment on attachment 8541436 That's pretty same to what described in Comment 4, 6, Hsiao-Ting's, and STR in Bug 1102121. Open any webpage, right click to page, click "另存新檔…" (Save As…), and observe the dialogĪll 6A,B,C produce same dialog with zh-CN translation. Open any webpage with link, right click to link, click "鏈結另存新檔…" (Save Link As…), and observe the dialogĦC. Open any webpage with image (e.g., ), right click to image, click "圖片另存新檔…" (Save Image As…), and observe the dialogĦB. Check the messages displayed inside the file picker (compare with the screenshots attached to Bug 1102121)ĦA. Go to Attachment: section and click the "瀏覽…" (Browse…) to add an attachment,ĥ. Open Bugzilla and try to file a new bugĤ. Have a Mac running with Yosemite, and switch system locale to Traditional Chinese (zh-TW, 繁體中文)ģ. > Peter, please provide your own, detailed STR - as detailed as Hsiao-Ting's.ġ. (In reply to Steven Michaud from comment #13) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |