- Mozilla - Llistes de Softcatalà

Fwd: Fixing v1.3 bugs
by Eduard Gamonal 15 Feb. '14

15 Feb. '14

Un recordatori per trobar els errors de la traduccio del firefoxos ---------- Missatge reenviat ---------- De: "delphine" <lebedel.delphine(a)gmail.com> Data: 12/02/2014 21.10 Assumpte: Fixing v1.3 bugs Per a: <dev-l10n(a)lists.mozilla.org> Cc: Hi there, Just a friendly reminder so you don't forget to go in and fixed identified bugs for v1.3 Here is the bugzilla dashboard where you can find your locale's bugs, and also look under FirefoxOS components to find them: http://mzl.la/LBCMNb Thanks :) delphine _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

3 4

Fwd: 1st round of l10n testing for FirefoxOS completed
by Eduard Gamonal 14 Feb. '14

14 Feb. '14

Resum de la situació al fx os. ---------- Missatge reenviat ---------- De: "delphine" <lebedel.delphine(a)gmail.com> Data: 10/02/2014 13.50 Assumpte: 1st round of l10n testing for FirefoxOS completed Per a: <dev-l10n(a)lists.mozilla.org> Cc: The first half of the v1.3 localization run has been completed on Friday (07/02) by QAnalyst testers and Mozilla community members. 2nd Round of QAnalyst testing will be from Feb.20 to Feb.26. (note that community testing is ongoing and will continue until the end of the 2nd round of testing) QAnalyst testing was performed on Buri device, using the latest 1.3 Moz RIL. Community testing was performed on latest Keon v1.3 builds. There is a total of 577 test cases for this Localization Run. Link to Localization Run: https://docs.google.com/spreadsheet/ccc?key=0AvRct4nrPb_ldHpIZnVneHlHVGhpWU… Locales covered during this first round: bit.ly/1cnBT1Q. Testing coverage is at 54.57% Localization Status * v1.3 l10n dashboard: https://l10n.mozilla.org/shipping/dashboard?tree=gaia-v1_3 * Croatian, Romanian and Macedonian still need to catch up with translation work. There has not been much traction from these communities, although we have reached out to them. Other locales are on track l10n testing * List of bugs identified: mzl.la/LBCMNb (226 bugs in total as of now) * List of truncation/text overlap issues: https://bugzilla.mozilla.org/show_bug.cgi?id=967050 Total: 121 bugs. This means 121 bugs out of the 226 identified are truncation/text overlap issues * List of 1.3? 1.3+: http://tinyurl.com/ppvpr52 Total of 5 bugs: * 968963 [Bengali]E.Me installed app suggestions display in English. (New) * 968998 [All Locales]E.Me Smart Collection list is displayed in english. (New) * 967708 [Settings] German: "Change PIN" doesn't use localization (Resolved Fixed) * 967857 [Gaia][Keyboard] Bengali: The Probhat keyboard for the Bengali language includes symbols that do not fit in the keyboard button. (Resolved Fixed) * 969193 [Cost Control] The string "OK" is not translated when launching cost control with a locked SIM (Verified fixed) delphine _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

1 0

[Mozilla.cat] Visita a cellers i calçotada mozil·liana l'1 de març
by Anna Rosich Soler 13 Feb. '14

13 Feb. '14

Oh, que xulo! Llàstima que coincideix amb Carnestoltes i per després de dinar tinc coses a fer. No em seria possible arribar a temps a Calella, argh. Que vagi molt bé!

1 0

Fwd: Re: new strings on 1.3, gaia-community on master
by Toni Hermoso Pulido 12 Feb. '14

12 Feb. '14

Ep, he pujat unes poques cadenes addicionals del Gaia al Pootle. Salut, -------- Missatge original -------- On 2/6/14 2:20 PM, Axel Hecht wrote: > Hi, > > I just pushed 10 new strings to 1.3, please get to those quickly. > > For gaia-community, I migrated that to /gaia-l10n/en-US, aka master. > That's 150 strings compared to the previous 1.3 status. > > Master is for 1.4, and the schedule for 1.4 is going to be different > than previous schedules. > > I'll have a few townhalls once we're actually sharing the schedule in > public. > > I removed 1.1 and 1.2 from the dashboards, those are wrapped up. > > Axel PS: The settings strings are developer debug strings, for the Async Pan Zoom Controller, APZC in short. Feel free to leave those in English, I expect those to get removed once APZC works flawlessly, too. Axel _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

3 8

Fwd: Bugzilla report for l10n bugs in v1.3
by Toni Hermoso Pulido 09 Feb. '14

09 Feb. '14

FYI Sembla que anem força bé amb el Gaia. Kudos per a en Jordi Serratosa! :) ---------- Forwarded message ---------- From: delphine <lebedel.delphine(a)gmail.com> Date: 2014-02-07 Subject: Bugzilla report for l10n bugs in v1.3 To: dev-l10n(a)lists.mozilla.org As for previous versions, here's the l10n bugzilla table report listing bugs founds per locale and their status: mzl.la/LBCMNb Bugs are either under your locale, or under FirefoxOS component. If you are the person who is going to correct the bug: once you have corrected the bug, please mark it as "Resolved Fixed" If you then go in and make sure it is in fact fixed on the device, you can go ahead and mark the bug as "Verified Fixed" in order to close the bug 1st half of localization testing will be completed by the end of today (PST time). Second half will start Feb. 20 - Feb. 26 -- Toni Hermoso Pulido http://www.cau.cat

2 1

Fwd: Bugzilla guidelines for l10n
by Josep Sànchez 09 Feb. '14

09 Feb. '14

Bones, Segurament molts ja ho sabreu, però pels pardals com jo, va bé saber-ho :) Salut. -------- Missatge Original -------- De: "Francesco Lodolo [:flod]" <flod(a)lodolo.net> Enviat: Mon Nov 25 14:33:02 CET 2013 A: Mozilla l10n Mailing List <dev-l10n(a)lists.mozilla.org> Assumpte: Bugzilla guidelines for l10n Hi, it's me again. I was originally going to write this in the message about Metro, but then I realized it was becoming way too long. During last week I had a glimpse of how messy the Mozilla Localizations product is in terms of pending bugs: 3 years old open bugs with no activity, fixed bugs still marked as NEW, etc. Imagine a component in Bugzilla as a garden: right now Mozilla Localizations resembles an abandoned garden. With wandering zombies in it :-) How can we improve this situation? I'm not sure if some of these features are available to all users, if not please let me know. *Follow your locale* If you're not doing it already, start following your own locale on Bugzilla and try to keep it as clean as possible. Every time someone opens a bug in this component, you'll receive a bugmail. 1. Login to BugZilla with your account and go to Preferences->Component watching (https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch ). 2. Select Product "Mozilla Localizations". 3. Click on your locale in the "Component" section. 4. Click Add. *Resolve bugs* If a bug is resolved, it should be marked as RESOLVED FIXED, then verified on the next build and marked as VERIFIED FIXED. Don't leave open bugs around (remember zombies?). *Check pending bugs* You can also perform a search for open bugs in your locales and save it: 1. Do an Advanced search on Mozilla Localizations -> Your locale for bugs with Resolution "---". 2. When results are displayed you'll see a "Remember search" button at the bottom of the page, give it a name (e.g. "Italian bugs"). 3. From now on you'll see a link in the footer of all Bugzilla pages to perform the same search. *Clear review and needinfo requests* If someone falgs you for a review, or set a NEEDINFO for you, you should try to clear these requests. 1. Reviews: click on the review link in the attachment section, chose "+" if the patch is good, "-" if is not, " " (blank) to reset the request if you shouldn't be reviewing the patch. 2. Needinfos: when you reply, below the comment you'll see a checkbox, already checked, saying "I am providing the requested information for YOURACCOUNT (clears the needinfo request).". If you're providing the information requested, leave it checked and comment. When you login to Bugzilla, you should see a red circle with a white number near the title Bugzilla@Mozilla. Behind these requests there are people, so be kind to them and reply ;-) Francesco _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n -- S’ha enviat des del meu telèfon Android amb K-9 Mail. Si us plau, excusa la meva brevetat.

2 1

Fwd: Firefox Aurora L10n Report (cycle 28)
by Eduard Gamonal 09 Feb. '14

09 Feb. '14

Informació del proper cicle! ---------- Forwarded message ---------- From: Jeff Beatty <jbeatty(a)mozilla.com> Date: Tue, Feb 4, 2014 at 7:27 PM Subject: Firefox Aurora L10n Report (cycle 28) To: dev-l10n <dev-l10n(a)lists.mozilla.org> Hello localizers! Thank you all for your great work with Firefox 27 and 28. Here's an outline of what is currently in Aurora this cycle (29) and what we accomplished together last cycle: This cycle (3 February - 17 March) Key dates include: - Beta sign offs must be completed before 10 March. - Aurora sign offs must be completed before 17 March. - Firefox 28 releases 18 March. Features: - Approximately 389 new string changes were added to Aurora desktop, 200 for Aurora mobile. - Many of the new desktop strings are in devtools and metro. They cover the implementation of Australis, devtools, and first run in Metro (see https://wiki.mozilla.org/Features/Release_Tracking#Desktop_.28Win.2C_Mac.2C_ Linux.2C_Metro.29_2). - Many of the mobile strings include preferences and renaming of all Sync strings for Firefox Accounts (see https://wiki.mozilla.org/ Mobile/Roadmap#Firefox_29:_.28Aurora.29 ). Notes: Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you're submitting for shipment. Last cycle (9 December - 3 February) Noteworthy accomplishments: - 70% of all locales shipped Firefox 26 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 8% increase in locale coverage between Firefox 26 and Firefox 27! - Aragonese and Xhosa had their first official release on Firefox desktop today with Firefox 27! Please join me in congratulating the teams! - South African English, Thai, Lithuanian, and Slovenian were launched in Firefox for Android with Firefox 27. If your locale is ready for shipping and part of Android's list of supported locales, please reach out to me to add you to the roadmap. Please join me in congratulating the teams! Thank you to everyone for all of your dedication and hard work this last sprint. As always, if you note anything missing in these reports, please let me know. Thanks, Jeff -- *Jeff Beatty* Localization Engineer @mozilla_l10n <http://twitter.com/mozilla_l10n> 801.367.3763 _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

1 0

[Mozilla.cat] Visita a cellers i calçotada mozil·liana l'1 de març
by Toni Hermoso Pulido 08 Feb. '14

08 Feb. '14

Hola gent, coincidint amb l'acabament del MWC 2014, en Marc Pareta (en CC) està mirant d'organitzar una una visita a cellers i una calçotada posterior al Penedès el dia 1 de març. En principi la invitació la faríem a tothom interessat en les tecnologies i món Mozilla a Catalunya i comptem poder tenir alguns visitants que hagin vingut durant el MWC 2014. En els propers dies anirem definint la logística! -- Toni Hermoso Pulido http://www.cau.cat

1 0

Problemes amb el ChatZilla.
by Pau Sellés i Garcia 07 Feb. '14

07 Feb. '14

Hola. Acabe d'actualitzar a la versió 27.x de Firefox i la versió en català del Chatzilla m'apareix no compatible. Toni, quan tingues un minut podries fer-li una ullada? -- Una salutació, ---------------------- Pau Sellés i Garcia pau.selles(a)josoc.cat ----------------------

2 3

Fwd: Please consider if your locale could default to UTF-8 for outgoing email
by Jordi Serratosa 31 Gen. '14

31 Gen. '14

Ep A la llista de traducció de Mozilla comenten que cada llengua caldria considerar si vol canviar la codificació de caràcters per defecte a UTF-8 en l'enviament de missatges de correu. Si voleu seguir la conversa, és aquí: <https://groups.google.com/forum/#!topic/mozilla.dev.l10n/PH7tF9m8vUY> Actualment, el català té configurat que els missatges s'enviïn per defecte en ISO-8859-1. En principi jo no veig inconvenients per fer el canvi, que sembla prou lògic, però no sé si algú en sap més i creu que no seria bona idea... Anybody? salut jordi s -------- Missatge original -------- Assumpte: Please consider if your locale could default to UTF-8 for outgoing email Data: Fri, 31 Jan 2014 12:30:13 +0200 De: Henri Sivonen <hsivonen(a)hsivonen.fi> A: dev-l10n(a)lists.mozilla.org, dev-apps-thunderbird(a)lists.mozilla.org Yesterday, the default character encoding for new outgoing email in the en-US localization of Thunderbird changed from ISO-8859-1 (which really means windows-1252 labeled as ISO-8859-1) to UTF-8. (Thanks Magnus!) Previously, many other localizations had already set the default character encoding for new outgoing email to UTF-8. This localizations are: Arabic Belarusian Greek Farsi Georgian Macedonian South Ndebele Panjabi Polish Romanian Russian Serbian Swati Southern Sotho Tsonga Venda Vietnamese Xhosa Traditonal Chinese Zulu Note that this isn't just a matter of African languages that have to use UTF-8 using UTF-8. The above list includes languages that do have Thunderbird-supported legacy encodings (Arabic, Belarusian, Greek, Farsi, Macedonian, Polish, Romanian, Russian, Serbian, Vietnamese, Traditional Chinese). I encourage other localizations to consider whether they'd be ready to change the default for outgoing email (mailnews.send_default_charset in messenger.properties) to UTF-8. The only reason not to would be regionally still-popular UTF-8-incapable email clients. (Unlikely at this day and age.) In particular, since the Belarusian, Macedonian, Russian and Serbian localizations have already been able to make the switch to UTF-8, it is very probable that the Bulgarian and Ukrainian localizations could do so, too, at this time. I'd also like to especially encourage the German, Italian and Breton localizations to consider if they could make the switch to UTF-8. These three locales currently default to ISO-8859-15 for outgoing email. This doesn't make sense, because: 1) ISO-8859-15 is a younger encoding than UTF-8. If you are worrying about UTF-8 being too new to be supported, on newness grounds, you should worry even more about ISO-8859-15! 2) Compared to ISO-8859-1, ISO-8859-15 was motivated by three things: less common French letters mysteriously omitted from ISO-8859-1, transliterations in the Finnish context (totally missing the point of transliterations!) and the euro sign. When the French and Finnish localizations as well as many other localizations used in the Eurozone don't need to default to ISO-8859-15, German, Italian and Breton almost certainly don't need to, either. But instead of changing back to ISO-8859-1, let's treat this as an opportunity to switch to UTF-8. - - Currently, Thunderbird already silently upgrades a message to UTF-8 even when the default is something else if the message contains characters that can't be expressed in the preferred legacy encoding, so it's not like the defaults prevent people from writing stuff in email. So why bother changing the default then? The reason why Thunderbird doesn't always use UTF-8 for outgoing email is that way back when UTF-8 support was initially added to email clients, older email clients out there didn't all already supports UTF-8, so it makes sense to use already-supported legacy encodings when possible. But that was a long ago. UTF-8 was invented over 20 years ago and at least for the past decade, the ability to receive UTF-8 has been commonplace. We should stop pretending that UTF-8 avoidance still adds value when pretty much everyone already uses email clients capable of receiving UTF-8. The Gaia email client already simply uses UTF-8 for all outgoing email. The UTF-8 avoidance capabilities don't come for free. In addition to having to maintain encoders for legacy encodings (which needs to happen to support form submissions in Firefox anyway) and having code complexity to deal with the silent upgrade to UTF-8 (which isn't that much additional code complexity considering what Firefox form submissions require anyway) it means having to maintain the capability of the HTML serializers (for HTML mail) to output encodings other than UTF-8 and it comes with the UI burden (both in terms of adding more stuff that the user may end up thinking about and in terms of adding a ball and chain legacy to code maintenance) since we seem to feel that if there is the possibility to use encodings other than UTF-8, there should be UI for it. (My primary interest in this is the inertia that Thunderbird having UI for this imposes on making encoding-related changes to Firefox.) So the two previous paragraphs seem to argue for removing the configurability and just always sending UTF-8. What's this about localizations changing the default configuration then? Changing the default configuration is a first step that makes reducing configurability and the associated code complexity less scary in the future. Making a change like this product-wide regardless of locale tends to bring up concerns that maybe the email client environment for some locale out there isn't ready yet. As more and more locales make the call that they can make the switch and default outgoing email to UTF-8, the concern of the form "Where *I* live, we don't have problems with this but I *worry* that *they* over *there* do." becomes less of a source of inertia. -- Henri Sivonen hsivonen(a)hsivonen.fi _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

3 2