Closed Bug 281530 Opened 20 years ago Closed 20 years ago

Typos in Czech Firefox 1.0

Categories

(Mozilla Localizations :: cs / Czech, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: p.franc, Assigned: p.franc)

Details

Attachments

(4 files)

The following patches fixed typos in Czech Firefox 1.0
Attachment #173759 - Flags: approval-aviary1.0.1?
Attachment #173760 - Flags: approval-aviary1.0.1?
This patch adds only correct queryEncoding/queryCharset and changes sourceid
from mozilla to firefox for Czech servers. No search plugin is removed/added.
Attachment #173761 - Flags: approval-aviary1.0.1?
This patch changes the sourceid from mozilla to firefox in Fast Search
bookmarks for Czech servers. No bookmark is added/removed.
Attachment #173762 - Flags: approval-aviary1.0.1?
Status: NEW → ASSIGNED
Sorry, no check-ins for released locales on the branch.

Please unset your approval requests, as I can't :-(.
Axel: Such policy (freeze of locale after release) make perfect sense in the
case of English locale, which is source for all other locales. If minor versions
of product are released to provide better version (in the terms of stability and
security), I think that L10N teams should be also allowed to polish their work.

If I'm right, 1.0.1 will be first minor release of localized product on stable
branch from MF and policies should be reconsidered for this new situation.

I would like to prevent users saying "You didn't correct errors we discovered
and noticed in previous version. Why?!" and of course provide perfect experience
with Firefox.
Whatever the argument is, please unset the 1.0.1 flags, they do not apply to 
localisations.

I do admit that we shouldn't release this policy bit by bit with bugzilla 
comments. We have a draft announcement cycling, but due to timeshifts and 
workload, it continues to slip.

1.0.1 is a security and top-crash-minor-risk update. The minor update to 1.0 
will be 1.1.
Given the amount of QA load that accepting l10n patches would induce, and the
delay of the 1.0.1 release because of that, some-sort-of-we agreed to not take
l10n related patches, unless they are in fact security relevant. Think of
parse errors in security-related dialogs, misleading translations in there.
This is a compromise, of course, but "we" think we have a decent logic behind
it.
Axel, okay. Pawell will unset request flags and mark this bug as WONTFIX?
Attachment #173759 - Flags: approval-aviary1.0.1?
Attachment #173760 - Flags: approval-aviary1.0.1?
Attachment #173761 - Flags: approval-aviary1.0.1?
Attachment #173762 - Flags: approval-aviary1.0.1?
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
There is no real need to wontfix this bug.

Any check-in to the cvs repositories should have a bug, so that others can see
why you changed what. So even if you fix these issues on the trunk, having this
bug open and using a check-in comment like "bug 281530, fix typos in cz-CZ, r=..."
(if you have someone who reviewed it, which is always a good idea) would be good
style.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: