Closed
Bug 354819
Opened 18 years ago
Closed 18 years ago
[mn] search-db.rdf has XML parsing error, firebird-toc.rdf not up-to-date
Categories
(Mozilla Localizations :: mn / Mongolian, defect)
Mozilla Localizations
mn / Mongolian
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: natsag2000)
Details
(Keywords: verified1.8.1)
Attachments
(1 file)
1.20 KB,
patch
|
Pike
:
approval1.8.1+
|
Details | Diff | Splinter Review |
<li><Description nc:name="Disabling, Enabling, Uninstalling Add-ons" nc:link="customization.xhtml#add_ons_uninstalling"/></li>
has a spurious ="" in there, which leads to a XML parsing error in search-db.rdf.
firebird-toc.rdf has several entries which are not resolved, in particular in cookies.xhtml, prefs.xhtml and customization.xhtml.
Those errors are shown by running my help-helper extension, available at http://people.mozilla.com/~axel/l10n/
Reporter | ||
Comment 1•18 years ago
|
||
Forgot to update my local tree, cookies.xhtml links are fixed.
themes, toolbars, getting_installing_themes in customization.xhtml, sanitize in menu_reference.xhtml and advanced_encryption, security_passwords in prefs.xhtml remain.
Reporter | ||
Comment 2•18 years ago
|
||
[mn] Landing the xml parsing error patch, this is a simple bustage fix, exactly the thing I planned to have Friday for.
Attachment #240607 -
Flags: approval1.8.1+
Reporter | ||
Comment 3•18 years ago
|
||
Adding fixed1.8.1 keyword, as there are check-ins with a corresponding bugnumber.
Please make sure that the bugs are VERIFIED, and if so, change the fixed1.8.1 keyword to verified1.8.1.
Your friendly bugspammer, moving stuff from the 2.0 triage radar.
Keywords: fixed1.8.1
Assignee | ||
Updated•18 years ago
|
Keywords: fixed1.8.1 → verified1.8.1
Reporter | ||
Comment 4•18 years ago
|
||
Natsagdorj, can you please land this on the trunk and mark this bug FIXED?
Assignee | ||
Comment 5•18 years ago
|
||
Hi Axel,
Sorry for late replying :(
The fixed file landed on the trunk.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•