Gener 2014 - Mozilla - Llistes de Softcatalà

Interessaria ampliar la traducció del "web" de Mozilla?
by Josep Sanchez 04 Maig '14

04 Maig '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bones, Mirant-me coses a partir de mozilla.org, m'he plantejat que igual hi ha apartat que seria interessant de traduir. No sé si ho creieu necessari, prioritari o secundari, però pàgines com les de |com es pot col·laborar amb el projecte», o la de donacions, si és que no hi ha cap impediment tècnic que no controli, trobo que ajudarien a difondre el projecte. Com ho veieu? Val la pena, o seria feina no productiva? Salut. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSpwqOAAoJEJBOJru8PbFKLxUP/3F/jH2e4JB7J09DHfRiAtH/ qowQCuD8L8/lMUyDwl7x7LjLYRRaL9an56zgoG8pWxzRQEJMC/DJAyqpdO9Tyoh9 OdLyx0xUcnxigiKZVi6MD0pm9Q8jEnZGj8QLuQbtyvuJVv65FHqU66dH2jGjZQMm wHx5WBVcPPBVb8cmC0PLFkeZK351LWm9PmWVDyLIhnU4Vpy2eu8OmdSxT410+tSU ACIf/IGwmsjX0y9H0x0ov75ij+AOx8sLiIVZVM3fjSa4gpnKpCE1RYAjbEPtTCkV gQCE30iJtHuVgvyCI1eE3cXsYGyUmYTNv4RmPhfEDXIfMAdOEHvvbh1zQwCFuaG7 dNZwDeZf2+GFF2Ty75FUqxtQW5rIyP74xItXK1u+dCqQb+/kgrHwSCdGTdvFRbn0 q/PR0YbqOyt1Gag2qBWD8KiNTOtzR6RzllZeQFRExvjs3/Qcdw2Ik3LWf4KXQCa1 2GNYBIRRQMOvMNCd0TQtPB5sDM9uZtYP0YlJxDwYcfMe87bp0atwNRoeKyAjkV9m 0x/YqHaidvruZIvDkwBwf3cT87bENf/fTNjNy4TRNwzTqd818PobZUVFVukF56AH 6+E/0xOk6Sj/djIhmfngaXZLbmlPLiZ4cuvL8z2+UcioRsWKZgeMPZx3SFW99qyL KL/UaFe+AzhvGFZrrVe2 =ux4e -----END PGP SIGNATURE-----

2 2

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: 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

Fwd: New strings uplifted to gaia and gaia 1.3
by Toni Hermoso Pulido 23 Gen. '14

23 Gen. '14

Hola, he aprofitat per actualitzar les cadenes al Pootle. Salut, -------- Missatge original -------- Hi, I've just pushed strings to gaia 1.3: 75 new strings, most of them flod's fault. They're adding optional strings for setting headers, which fall back to the button titles. copy-n-paste is gonna get you a long way here, and then you can start fixing. I also updated gaia-central, though not to the current tip. Sadly there are strings that don't seem to be ready at all in the way, so I filed bug 960130 to get those into shape. Sadly, we're also missing out on fixes to strings I exposed now this way, but this has been a choice of pest and cholera. Axel _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

2 2

[Mozilla.cat] Fwd: New location for release calendar
by Jordi Serratosa 22 Gen. '14

22 Gen. '14

Ep No sé si això afecta el calendari de "Properes versions" que hi ha a http://mozilla.cat/ salut jordi s -------- Missatge original -------- Assumpte: New location for release calendar Data: Wed, 15 Jan 2014 18:58:05 +0100 De: Axel Hecht <l10n(a)mozilla.com> A: dev-l10n(a)lists.mozilla.org Grups de discussió: mozilla.dev.l10n For those of you enjoying the noise on the release calendar, it's now in a new location: https://mail.mozilla.com/home/publiccalendar@mozilla.com/Releases%20Schedul… Axel _______________________________________________ dev-l10n mailing list dev-l10n(a)lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n

4 8

Dubtes de traducció ("Mobilizer" i "Look ahead")
by Anna Rosich Soler 11 Gen. '14

11 Gen. '14

Hola! Estic traduint la home page i hi ha un parell de cadenes que contenen eslògans. L'Eduard m'ha comentat que encara no s'havia decidit quina en seria la traducció. Hi he estat pensant i us voldria proposar les meves traduccions, a veure què us semblen. 1) "Become a Mobilizer today." En Pascal m'ha dit això: "so there is a play on words on this one because it means engaging people (to mobilize) but also to get them on mobile (Android / FxOS)" Així doncs, jo aviat pensat de traduir "Mobilizer" com "mobilitzador", del verb "mobilitzar" i de la paraula "mòbil". 2) "Look ahead" He fet una traducció literal i també m'he basat en les traduccions d'altres idiomes per a aquesta cadena: Die Zukunft im Blick / Mira hacia el futuro / Regardez l'avenir / Contempla l'avegnir Què us sembla "Mireu cap al futur". No tinc clar que com a eslògan funcioni... Tota aportació o crítica serà benvinguda :-) Anna

7 32

Noves cadenes al Pootle - Mozilla i Gaia
by Toni Hermoso Pulido 11 Gen. '14

11 Gen. '14

Hola gent, noves cadenes al Pootle: http://pootle.softcatala.org/projects/gaia/ Gaia - Firefox OS - Més per a la versió 1.2 http://pootle.softcatala.org/projects/mozilla Firefox, Thunderbird, etc. (versió 27) Salut, -- Toni Hermoso Pulido http://www.cau.cat

6 23

/firefox/os/faq.lang
by Josep Sanchez 10 Gen. '14

10 Gen. '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 L'agafo! Salut. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS0HScAAoJEJuo2ANsrVnjL6kH/jX7AdnNLhjQQAL0PuFnSzF1 mFAU3LDI+btXvQJ865f3deytUW7jT4+ybrI7Av91kP5/1xWPFU2TvNglj4f2vhux gLBkL4nPA+R50TEdVQdBKwEQcksR6acP6Tceyb8zOSJwcCZY3uBlEJ1VI4k7HMjB BtqWZD0tAkmP+3c3+V2a98ut6WkoEBKhnmmCse/N/KEaH6tzWY+b7QyxZSFaYAOp AlQ9nwQ4xdHqOUKxxhWWDPASoqxdZAwVLOmqMfAw10ml83GJvCPK2pliAOPiFyKE zY9ZDQ6g9JnkEtNlU4pa9AYCohA7po86sdyFgP8kQO3RvOhm/bDwrFWP/bympGA= =OQJ9 -----END PGP SIGNATURE-----

1 0