Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

broken XML prettyprint in 1.2.1?

4 views
Skip to first unread message

Jason A. Lefkowitz

unread,
Dec 3, 2002, 11:57:47 AM12/3/02
to
Hey all...

I've been happily using the new preference for XML prettyprinting since
1.2a was released. Specifically, I added this into my user.js file:

user_pref("layout.xml.prettyprint", true);

... and presto, XML files were prettyprinted. I just moved up to 1.2.1,
however (from 1.2 final), and now the prettyprinting no longer seems to
work. I checked the bug in Bugzilla (#64945) and it appears that I'm
not the only one encountering this: problems with prettyprint in 1.2
were reported on OS X and Mandrake (I'm on Windows 2000). No "official"
confirmation has been posted, though, and the 1.2.1 Release Notes
(http://www.mozilla.org/releases/mozilla1.2.1/) list XML prettyprint as
a new feature of 1.2.1.

So, does anyone know what gives? Is prettyprint broken, has the
user_pref been changed/disabled, or is there something else going on?
Thanks in advance for any assistance!

Sincerely,

Jason Lefkowitz

Jonas Sicking

unread,
Dec 4, 2002, 1:14:06 AM12/4/02
to
I havn't yet had time to investigate this, but i'll try to get to it as
soon as possible. It's probably too late to get a fix in for 1.3a, but
i'll try to get it done for 1.3b.

/ Jonas Sicking

Dimitre Novatchev

unread,
Dec 8, 2002, 3:42:11 AM12/8/02
to

"Jason A. Lefkowitz" <jalef...@aol.com> wrote in message
news:asindh$4b...@ripley.netscape.com...

> Hey all...
>
> I've been happily using the new preference for XML prettyprinting since
> 1.2a was released. Specifically, I added this into my user.js file:
>
> user_pref("layout.xml.prettyprint", true);
>
> ... and presto, XML files were prettyprinted. I just moved up to 1.2.1,
> however (from 1.2 final), and now the prettyprinting no longer seems to
> work.
...................................
I already mentioned in a previous post that one such case was not displaying
namespace definitions.

Another type of this is when the source xml contains text with (correctly)
escaped ampersand.
The prettyprinter displays an unescaped ampersand, which makes the result
non-well formed.

For example:

<company>M &amp; M</company>

wil be displayed as:

<company>M & M</company>

If it is a consolation, IE has the same behaviour when displaying xml files
...


These two problems are fixed in the XPath Visualizer for Mozilla, which will
be released in the nearest future.


=====
Cheers,

Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL


0 new messages