Closed
Bug 313392
Opened 20 years ago
Closed 19 years ago
Localizable files for reporter should be moved from main source tree to /l10n
Categories
(Mozilla Localizations :: Other, defect)
Mozilla Localizations
Other
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla2.0
People
(Reporter: sskroeder, Assigned: Pike)
Details
(Keywords: fixed1.8.1)
Attachments
(2 files)
4.76 KB,
patch
|
benjamin
:
review+
raccettura
:
review+
|
Details | Diff | Splinter Review |
118.13 KB,
patch
|
Details | Diff | Splinter Review |
Currently the localizeable files for the reporter resides in the main source
tree (along the XUL code for the feature) -- those files should be moved to the
/l10n tree, since reporter no longer is considered an extension...
Assignee | ||
Comment 1•20 years ago
|
||
It'd be probably a good thing to have robert and bsmedberg confirm this.
Comment 2•20 years ago
|
||
This is correct.
Assignee | ||
Comment 4•19 years ago
|
||
The upcoming patch requires to back-port the localizations for
bg, de, and eu;
The localizations for
ca, cs, da, el, es-AR, fi, fr, ga-IE, gu-IN, he, hu, hy-AM, ko, mk, mn, nb-NO,
nl, pa-IN, ro, ru, sk, sl
differ.
I'm taking nominations on what to do with those. You can choose between
back-port and leave-alone for trunk, I'll back-port for moz18.
This is basically in order to have control over the changes between 1.5 and 2.
I'm not sure if I target the 1.5.0.x releases right now for the /cvsroot
changes. It may be good to have it in a second step if we want to take new
locales on the 1.5.0.x route. Which would be good.
OS: Linux → All
Target Milestone: --- → mozilla1.9final
Comment 5•19 years ago
|
||
Regarding cs, the localization in l10n tree of trunk and 1.8 branch is the correct one. There was a bug 313678 to update the main tree but it came too late.
In fr, the difference is negligible (just one word AFAICT). You can either include or ignore the changes depending of what is easier for you.
Comment 7•19 years ago
|
||
Axel, is this bug in scope for 1.5.0.1? If so, what needs to happen to nail it to the wall?
Comment 8•19 years ago
|
||
No, this is not in scope for 1.8.0.1 and unless there are overwhelming arguments I'd argue not for 1.8.0.x at all. Let's do this on 1.8/trunk.
Assignee | ||
Comment 9•19 years ago
|
||
I just landed the reporter files for fy-NL and lt on the 1.8.0 branch to get those
locales in better shape for the fx 1.5.0.x release cycle.
Assignee | ||
Comment 10•19 years ago
|
||
This is the fix to the actual reporter files, I didn't attach the changes to the
localizations.
I tried to move the Makefiles as close to the standard set by dom, netwerk etc,
removing the NO_JAR_AUTO_REG in favour of moving the contents.rdf into the
seamonkey part of the jar.mn.
Attachment #209482 -
Flags: review?(benjamin)
Assignee | ||
Comment 11•19 years ago
|
||
I checked in the current state of reporter in /cvsroot on the
MOZILLA_1_8_BRANCH. I'm going to leave trunk alone, but I would like to bootstrap
our Firefox 2 developement with the state of the localization that fx1.5 has.
This includes line ending fixes etc.
I tagged the tree afterwards for reference. The affected locales are
bg ca cs da de el es-AR eu fi fr ga-IE gu-IN he hu hy-AM ko mk mn nb-NO nl pa-IN pt-BR ro ru sk sl
I checked this in in preparation of the opening of the 1.8 branch for 2.0
developement, this is getting time critical and the actual build foo doesn't
go in fast enough.
Affected locales are invited to take a close look at the actual changes I did
to see what they should do with their local changes. Please don't just plain
revert, you may add back line ending bustages or the like.
A sample bonsai query for the changes would be (for bg),
http://bonsai-l10n.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_1_8_BRANCH&branchtype=match&dir=l10n%2Fbg%2Fextensions%2Freporter&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-01-27+5%3A00&maxdate=2006-01-27+5%3A45&cvsroot=%2Fl10n
Once you checked that I didn't change something useful, you may want to look at
the "Show commands which could be used to back out these changes" link to show
how to get back to your old version.
Updated•19 years ago
|
Attachment #209482 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 12•19 years ago
|
||
Comment on attachment 209482 [details] [diff] [review]
fix reporter build logic
Requesting approval and second review from Robert for landing on the 1.8 branch and trunk
Attachment #209482 -
Flags: review?(robert)
Updated•19 years ago
|
Attachment #209482 -
Flags: review?(robert) → review+
Assignee | ||
Comment 13•19 years ago
|
||
Checked in on trunk and MOZILLA_1_8_BRANCH
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 14•19 years ago
|
||
Verified.
Trunk l10n tinderbox is green at last. :)
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 15•19 years ago
|
||
removed the stale localizations in mozilla/extensions/reporter, too.
Filed bug 326348 about actually running compare-locales on reporter again.
Keywords: fixed1.8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•