Closed
Bug 485691
Opened 16 years ago
Closed 6 years ago
Compare-locales fails for Venkman if *.accesskey is specified in l10n
Categories
(Other Applications Graveyard :: Venkman JS Debugger, defect)
Other Applications Graveyard
Venkman JS Debugger
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: dev-null, Assigned: rginda)
References
Details
Bug 479688 adds a feature that can specify accesskey with keys named *.accesskey.
But if *.accesskey is added in l10n, compare-locales.pl fails at
http://hg.mozilla.org/venkman/file/a18bc7edd2fd/locales/Makefile.in#l85
because it does not match with en-US strings.
Then, the build will fail.
So either of these is required:
- The build should success even if compare-locales.pl fails.
- All l10n, including en-US, should use *.accesskey.
Which way is better?
Comment 1•16 years ago
|
||
Venkman doesn't seem to have this problem, the original bug is a landing only for chatzilla.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> Venkman doesn't seem to have this problem, the original bug is a landing only
> for chatzilla.
The patch in Bug 479688 is already granted. So Venkman will have the same problem soon.
That's a reason why this bug blocks Bug 479688.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 3•16 years ago
|
||
Looks like this needs the same treatment as ChatZilla. Which pretty much sucks, but oh well... :-\
Status: REOPENED → NEW
Summary: Build fails if *.accesskey is specified in l10n → Compare-locales fails for Venkman if *.accesskey is specified in l10n
Comment 4•6 years ago
|
||
Component is obsolete so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Closed: 16 years ago → 6 years ago
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•