Closed
Bug 760998
Opened 12 years ago
Closed 12 years ago
[compare-locale] Error on crashreporter.ini with MPL2 boilerplate followed by empty line
Categories
(Mozilla Localizations :: Infrastructure, defect)
Mozilla Localizations
Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: flod, Assigned: Pike)
References
Details
Italian file http://hg.mozilla.org/l10n-central/it/file/c7bee6ec8ca3/toolkit/crashreporter/crashreporter.ini compare-locales generates this error Unparsed content "; This Source Code Form is subject to the terms of the Mozilla Public ; License, v. 2.0. If a copy of the MPL was not distributed with this ; file, You can obtain one at http://mozilla.org/MPL/2.0/. [Strings]" at 0-209 Adding this comment makes the error disappears # This file is in the UTF-8 encoding
Assignee | ||
Comment 1•12 years ago
|
||
My suspicion is that http://hg.mozilla.org/l10n/compare-locales/file/f4effbecaaec/lib/Mozilla/Parser.py#l355 doesn't allow the empty line in that constellation. Path to fix would be to mimic the tests in http://hg.mozilla.org/l10n/compare-locales/file/f4effbecaaec/lib/Mozilla/tests/unitProperties.py, verify that it breaks, and then patch. In other words, this is a nice patch for someone to start hacking on compare-locales.
Comment 2•12 years ago
|
||
Seeing that on https://l10n.mozilla.org/dashboard/compare?run=224504 as well, and there the empty lines come from the originals, see http://hg.mozilla.org/comm-central/file/4efc4d422213/suite/locales/en-US/crashreporter/crashreporter-override.ini and http://hg.mozilla.org/comm-central/file/4efc4d422213/suite/locales/en-US/updater/updater.ini
Summary: [compare-locale] Error on crashreporter.ini when UTF8 comment is missing → [compare-locale] Error on crashreporter.ini with MPL2 boilerplate followed by empty line
Assignee | ||
Comment 3•12 years ago
|
||
http://hg.mozilla.org/l10n/compare-locales/rev/98efaa127844, FIXED. I also updated the seamonkey runs for central and aurora.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•