Closed Bug 584375 (fxhome-l10n-pl) Opened 15 years ago Closed 15 years ago

[tracking] [pl] Localize the Firefox Home Project into Polish

Categories

(Mozilla Localizations :: pl / Polish, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sethb, Assigned: marcoos)

References

Details

This bug will be used to track your locale's progress toward localizing the various aspects of the Firefox Home project. Keep in mind that the work you do for this project will only take effect if the iPhone OS is supported in your language. If you have any doubts, be sure to ping the dev-team (cc-ed here) in this bug to confirm. We will file individual bugs for each piece of the project needing l10n. This will include bugs for the app, website, and other one-off parts for this unique iPhone-based process. All files and other attachments will be placed in the master Firefox Home tracking bug (bug 583241) that this individual locale tracking bug is blocking. Throughout the project, when we reference files or other pieces for review, be sure to check bug 583241. Because of the unique nature of this project, I have cc-ed the developer lead (Dan Walkowski) and the project manager (Ragavan Srinivasan) to this bug. Dan, Ragavan, and the l10n-drivers are available to help answer questions.
Alias: fxhome-l10n-pl
Depends on: 584392
Depends on: 585047
Depends on: 585275
Depends on: 585588
No longer depends on: 585588
Depends on: 585900
QA Contact: akalla → kstawarz
Initial translation done in r72215. Still need to translate word plays like "Get up and go" and "Your Home on the Go".
Styling might need some fixes, as the design assumes that the fragments of text over the three iPhones are the same height, which is true for en-US, but not for pl.
Some additional fixes in several revisions; r72224 is the most current one at the moment. Note that we're also taking care of the whole /mobile site, which hasn't been done for Polish up until now. Currently I've only commited the /mobile/home page for this bug (in its current, incomplete state), but I'm planning to have the whole /mobile secton this week. I hope it will be possible to publish /mobile/home as soon as needed, regardless of whether /mobile is done or not.
I can push pl/mobile/home tomorrow
Damn, these comments should have gone to the website bug, not this one. :/
For testing the App on a device, I will need each locale to provide me with the GUID number from one Apple iPhone 3, 3GS or 4 OR an iPod touch. Apple has allocated us a very limited number of testing slots for our beta program so we cannot make a universal build for everyone. Please email me (sethb@mozilla.com) the GUID number and your exact device/model description so we can set you up in the Apple beta testing system.
I've just sent my device ID to Seth.
Sent my GUID as well.
We are code freezing the *application* on Monday, August 16 at 16:00 PDT (UTC -7). Please have all of the application strings translated by that time. If you have any edits, please make them by that time and notify me.
Depends on: 587012
What is the proper character encoding for emails in each locale? e.g. utf-8 is not the standard for emails, in Japan, ISO-2022-JP is best [1] [1] https://bugzilla.mozilla.org/show_bug.cgi?id=585909#c5
I haven't heard about any problems with the UTF-8 encoding for Polish-language email for a few years. Thunderbird, Postbox, Mail.app and Microsoft mail clients fully support it, so does Opera Mail, Evolution, the Bat, GMail and all the significant local webmail providers (like Interia, Onet and WP.pl). If we tried to be overzealous, ISO-8859-2 (Latin-2) would be the choice. And it would certainly be the best choice in the year 2001. Personally, I think sticking with UTF-8 for Polish (and probably other Central Euro languages) is the way to go, but if we're really afraid that some people might be using pre-2001 e-mail clients, then I'm ok with ISO-8859-2, too.
BTW, in the olde days, Polish email encoding was always a mess, since the official legally approved standard was ISO-8859-2, but Microsoft never seemed to care about it. Old Outlooks used to send emails encoded in Microsoft's own screwed up CP1250 encoding, so most of the emails send were never in the correct encoding anyway, actually.
Firefox Home is now available for testing. In order to make it accessible to as many people as possible who may not have an iPhone, we set up a remote machine with the iPhone emulator to test the app. We will not be using GUID numbers, as we had thought earlier. To log in to the remote machine, you will need a remote desktop viewer client, sometimes referred to as a VNC. If you do not have a VNC client, you can download realvnc or tightvnc (viewer only). Google for "Tightvnc Viewer". On Ubuntu, it should be located in Applications --> Internet --> Remove Desktop Viewer. Once you launch the VNC application, it should ask for a hostname. You will need to enter "l10n-fxhome.community.mozilla.com". This is where we have set up a VM with Mac OS and the iPhone emulator. You will be asked for a password, so you will need to email me so I can share with you the password. Instructions on testing are visible in an open document on the remote desktop. You will immediately notice that multiple users can access this *one* machine at the same time. Therefore, be sure to state what localization is testing at the time you are testing. Any questions, please email me. sethb@mozilla.com
Sorry for being slightly late - I tested the app and it looks OK. :)
I am going to mark this as fixed, just to do some housekeeping. Since we are done with this version of the project, let's close this. If we have to reopen it for future work, let's do it.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
New strings have landed for the next release of Firefox Home (1.0.3). I will reopen this and leave it open to track future work for your locale.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
So, this bug will remain in the REOPENED state as long as new FxH releases are coming?
I can reopen it later if needed.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.