Closed Bug 583248 (fxhome-l10n-es-ES) Opened 14 years ago Closed 13 years ago

[tracking] [es-ES] Localize Firefox Home into Spanish

Categories

(Mozilla Localizations :: es-ES / Spanish, defect)

Product:
Mozilla Localizations
Component:
es-ES / Spanish
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sethb, Assigned: rpmdisguise-nave)

References

Details

This bug will be used to track your locale's progress toward localizing the various aspects of the Firefox Home project.  

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 583421) 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 583421.

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-es-ES
Depends on: 583266
Depends on: 584386
Depends on: 585040
Depends on: 585895
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.
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: 587005
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
(In reply to comment #4)
> 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'm not sure I'm getting this right... If the e-mail is sent with the proper charset header, using UTF-8 shouldn't be a problem for any decent mail agent, or am I wrong?

Anyway, nowadays both UTF-8 and ISO-8859-15 (which is like ISO-8859-1, but with the Euro sign) will work without any problem for Spanish.
(In reply to comment #5)
> (In reply to comment #4)
> > 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'm not sure I'm getting this right... If the e-mail is sent with the proper
> charset header, using UTF-8 shouldn't be a problem for any decent mail agent,
> or am I wrong?

I don't know the answer to this point, but since he raised it initially, perhaps Dynamis can answer your questions.
Hi Ricardo,

UTF-8 is very new charset compared to the email history. In some country they use their own charset for emails still now.
UTF-8 support cost is not so small especially for multi-byte languages. Changing charset takes really long time because we should think about backward compatibility.

In Japanese case, we traditionally use ISO-2022-JP charset for emails and most of Japanese mails are still ISO-2022-JP. Thunderbird and other modern email clients support UTF-8 but unfortunately there are still not a few email clients which doesn't support UTF-8. Some famous webmail service (ex. Yahoo! Japan mail), most of mobile phone don't support UTF-8 yet.
# note: Japanese mobile phone support many features including HTML mail,
# emoji (image chars) but they don't support UTF-8 yet (since they don't need).

That's why we should avoid sending japanese mail with UTF-8.
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
Marking as RESOLVED FIXED, as all blocking bugs are closed now. Please, reopen if I've done something wrong.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
I shouldn't have marked RESOLVED FIXED this bug because there is still a blocking bug open (585895), which is waiting for comments/confirmation from Seth/Alex.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
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: REOPENED → RESOLVED
Closed: 14 years ago → 14 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 → ---
Should we close this bug, right?
(In reply to comment #13)
> Should we close this bug, right?


Hard to tell. Seth's plans were to keep this bug open to track Fx Home L10n work, but now that he is gone, I'm not sure. I think I'll wait until next Fx Home release.
Closing as per comment #45 in bug 583241.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.