Closed
Bug 279812
Opened 20 years ago
Closed 20 years ago
Set up LXR service for l10n trunk
Categories
(Mozilla Localizations :: Other, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: chase, Assigned: chase)
References
Details
Users of the l10n repository require a trunk LXR installation to help them do
their work. Create a new LXR installation on mecha for this.
| Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•20 years ago
|
||
This is set up on mecha at:
http://lxr.mozilla.org/l10n/
It doesn't appear that there are any l10n files on the trunk, though, so the
installation is still empty. As such, I'm going to leave it off the main LXR
page for now.
Comment 2•20 years ago
|
||
I'd like to set similar request to bug 279811 Comment 4 in advance.
> could we get the page encoding set to utf-8? As the majority of our l10n files
> should be compatible with that. (My search results looked odd in ISO.)
Comment 3•20 years ago
|
||
(In reply to comment #1)
> It doesn't appear that there are any l10n files on the trunk, though, so the
> installation is still empty. As such, I'm going to leave it off the main LXR
> page for now.
Something is not OK here.
There is no-NO already in CVS but lxr does not show it.
| Assignee | ||
Comment 4•20 years ago
|
||
(In reply to comment #3)
> Something is not OK here.
> There is no-NO already in CVS but lxr does not show it.
I have looked at the CVS repository files on cvs.mozilla.org directly. There
isn't a no-NO locale in the mozilla module in /l10n. Can you post the results
of running:
sh$ cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/l10n co -P mozilla/
In my case, there is no mozilla/ directory present after this command completes
because no files exist within it on the trunk.
On the off-chance that you have been committing your files to the module "l10n"
in the l10n repository, yes, there are nb-NO and pl-PL locale files present on
the trunk. I note that the directory structure of what's been committed in this
module is different from what's historically been in the mozilla module.
Compare the results of this command (which is used to pull the locales during
the Firefox 1.0 build):
sh$ cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/l10n co -r
AVIARY_1_0_20040515_BRANCH mozilla/
with this command:
sh$ cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/l10n co l10n/
Is the change in directory structure intended?
I thought trunk files would also be committed to the mozilla module but perhaps
that is a flawed assumption. If the change in module is intended, I can alter
the trunk LXR to point at the l10n module instead of the mozilla module.
Comment 5•20 years ago
|
||
(In reply to comment #4)
> (In reply to comment #3)
> > Something is not OK here.
> > There is no-NO already in CVS but lxr does not show it.
nb-NO, pl-PL landed, too.
>
> sh$ cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/l10n co -P mozilla/
> sh$ cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/l10n co l10n/
This is the one. Yes, we're not in the same top-level-directory.
Comment 6•20 years ago
|
||
the l10n module is correct. We switched to avoid the problems with "overlaying"
two separate cvs trees on top of eachother.
Comment 7•20 years ago
|
||
it works for me ATM.
| Assignee | ||
Comment 8•20 years ago
|
||
LXR has some built-in usage of mozilla/ as the displayed module. I'd rather not
take this service down and hold up its use just because of that.
Please file a separate bug for the utf-8ification of LXR results and set this
bug as depending on that one. I'm not certain how long that bit would take but
I'd rather not let it fall out of sight.
Comment 9•20 years ago
|
||
filed bug 281362 for the utf-8 issue.
Comment 10•20 years ago
|
||
Let's mark this one FIXED, then.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•