282067 - Update firefox translation

Status: RESOLVED INVALID

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

Description

[Oscar Manuel Gómez Senovilla]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.5) Gecko/20041217

There have been many changes since 1.0 relase.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Oscar Manuel Gómez Senovilla]

Attachment: Attachment for toolkit branch

Comment 2

[Oscar Manuel Gómez Senovilla]

Attachment: Update patch for browser tree

Comment 3

[Axel Hecht]

Have you read
http://groups-beta.google.com/group/netscape.public.mozilla.l10n/browse_thread/thread/0afdeacd6e923aac/a0d4488e5fdba773#a0d4488e5fdba773
?

Seems like you didn't.

Comment 4

[Oscar Manuel Gómez Senovilla]

Ok, if you don't want to update the translation and have an outdated and buggy
translation, it's up to you.

If there's something I'm missing, please be more explicit.

Comment 5

[Robert Kaiser]

We _ONLY_ take changes to aviary if either it's a new locale or if it fixes a
security problem (e.g. wrong wording on a security-related dialog).

All other improvements are welcome, but won't go into the aviary 1.x branch,
they have to go into trunk.

Comment 6

[Pascal Chevrel:pascalc]

Oscar, 1.0.1 is a security/stability fix release, not a "product" release. The
only localisation fixes that might be accepted are bugs that would make the
product unstable or some of its features broken. For example if in 1.0 you had
translated something that you shouldn't have translated (like translating a
'true' boolean value to 'verdad') and that this incorrect translation makes some
visible feature buggy or makes Firefox crash, a patch fixing it *might* be accepted.

Otherwise, language patches won't be accepted because the priority is to fix our
security holes and release 1.0.1 with all security patches as soon as possible
before they get exploited by spyware, viruses or phishing sites.

Personnally I would mark the bug as invalid, not because improving localization
isn't important (we have strings in the FR build that we'd love to see corrected
as well ;) ) but simply because it is not what 1.0.1 was meant for and accepting
localization improvements would delay the planned release.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Comment on attachment 174171 [details] [diff] [review]
Attachment for toolkit branch

This should be asking for approval-l10n, not approval-aviary1.0.1

Comment 8

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Comment on attachment 174172 [details] [diff] [review]
Update patch for browser tree

This should be asking for approval-l10n, not approval-aviary1.0.1

Comment 9

[Zibi Braniecki [:zbraniecki][:gandalf]]

Comment on attachment 174171 [details] [diff] [review]
Attachment for toolkit branch

es-ES was released for 1.0.

Comment 10

[Zibi Braniecki [:zbraniecki][:gandalf]]

Comment on attachment 174172 [details] [diff] [review]
Update patch for browser tree

also here.

Please, do your work for 1.1

Comment 11

[Andrés G. Aragoneses]

Bug outdated (it affected 1.0 version).