XML parsing Error while try to open Wrong Page

RESOLVED FIXED

Status

Mozilla Localizations
pa-IN / Punjabi
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: A S Alam, Assigned: A S Alam)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
Product:
firefox-3-beta5
Build: 2008032619 
Open following link
http://buzilla.mozilla.org/  (Wrong Address)

Result:
XML ਪਾਰਸਿੰਗ ਗਲਤੀ: ਨਾ-ਸਮਕਾਲੀ ਐਨਟਟੀ
ਟਿਕਾਣਾ: jar:file:///home/aalam/firefox/chrome/toolkit.jar!/content/global/netError.xhtml
ਲਾਇਨ ਨੰਬਰ 246, ਕਾਲਮ  33:        <div id="ed_nssBadCert">&nssBadCert.longDesc2;</div>
--------------------------------^
(Assignee)

Comment 1

10 years ago
hi Axel,
please help where 
Blocks: 415646

Comment 2

10 years ago
http://bonsai-l10n.mozilla.org/cvsblame.cgi?file=/l10n/pa-IN/dom/chrome/netError.dtd&rev=1.11&mark=64-67#64 is the culprit, the entry misses closing tags for both the li and ul.

Note to me, myself, and I: The browser overload overloads netErrorApp.dtd, not netError.dtd. Why the hell.
(Assignee)

Comment 3

10 years ago
Thanks Axel,
sorry for bad question, but Is there time to fix Directly in cvs now or should I submit patch for this in bug?

Status: NEW → ASSIGNED

Comment 4

10 years ago
You can land that directly. If you want to, you can attach the fix as patch here for reference, but that's not necessary.

You might want to post the check-in output, that mumbles from which version to which version you got, so you have a link to the change here in the bug, and mention this bug in your check-in comment, that's easy to do and adds value.
(Assignee)

Comment 5

10 years ago
Created attachment 314328 [details] [diff] [review]
patch for netError.dtd

attaching patch, which going to check-in in cvs now...
(Assignee)

Comment 6

10 years ago
commited with following message:
-------------------
Checking in chrome/netError.dtd;
/l10n/l10n/pa-IN/dom/chrome/netError.dtd,v  <--  netError.dtd
new revision: 1.12; previous revision: 1.11
done
-----------------
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.