Closed
Bug 325924
Opened 19 years ago
Closed 19 years ago
compare-locales gets confused on #ifdefs
Categories
(Toolkit Graveyard :: Build Config, defect)
Toolkit Graveyard
Build Config
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: marcoos, Unassigned)
References
()
Details
Fix for bug 320504 introduced #ifdefs into l10n files:
#ifdef OFFICIAL_BRANDING
#define BRAND_PRODUCT_NAME Mozilla Firefox
#else
#define BRAND_PRODUCT_NAME Deer Park Alpha 2
#endif
This confuses compare-locales (it reports that BRAND_PRODUCT_NAME and some others are missing in the localization, while actually they are there twice) and makes l10n tinderbox orange at best.
Example of a build log with compare-locales whining about uninstaller.inc's #ifdef-ed strings:
http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-pl/1139085120.29861.gz&fulltext=1
| Reporter | ||
Comment 1•19 years ago
|
||
Sorry, the URL to the tinderbox was wrong. The one I meant was:
http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-pl/1139089800.20058.gz&fulltext=1
Comment 2•19 years ago
|
||
It's because compare-locales always reports a missing string if the string appears in file more than once. Even if it appears in both files equally. Fixing it would fix this bug.
Comment 3•19 years ago
|
||
I don't see us supporting #ifdefs reliably in the toolchain.
Let alone QA it. If someone has a working solution for it, reopen.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Comment 4•19 years ago
|
||
(In reply to comment #3)
> I don't see us supporting #ifdefs reliably in the toolchain.
>
> Let alone QA it. If someone has a working solution for it, reopen.
>
Pike, in case of this file, it will make tinderbox ALWAYS orange, do we want this?
| Reporter | ||
Comment 5•19 years ago
|
||
Gandalf:
compare-locales now ignores uninstaller.inc, see bug 320504 comment 47, so it's not making tboxes orange (trunk tboxes are now burining only due to reporter l10n SNAFU).
Updated•6 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•