hi Del,
On 12/03/2009 18:50, Del Merritt wrote:
Dear Dev team -
I am diving into OOo's source and the kind folk (thanks caolan) at
#dev.openoffice.org suggested I take my questions here.
nice to know you're interested in diving into the code!
By way of introduction, I am looking to see how to fix formatting bugs -
in particular, I have ".doc" documents that do not present the same way
in OOo as they do in the tool in which they were created. These
documents were explicitly created as "torture tests". Unfortunately I
cannot - for now - provide these documents to the OOo Issue tracker.
As an example, I have a six-page document that opens in OOo 2.3 (Linux)
and 2.4 (Windoze); while it renders somewhat correctly, there are
several severe formatting problems. With OOo DEV300_m43, built in a
manner similar to erAck's, the document takes a long time to open and
the process is littered with popups indicating a variety of problems -
see below or http://ooo.pastebin.ca/1359053 - and if I click on the "No"
options (ignore error and continue) enough times, the document
eventually loads and renders, mostly similar to the 2.[34].
about the popups:
these come from assertions. there are several different assertion
mechanisms used in OOo; one is OSL_ENSURE and friends from osl/diagnose.h,
another is DBG_ASSERT and friends from tools module, and the sw module has
its own mechanism ASSERT.
most of these are only enabled in non-product builds.
if the popups bother you: you can get a debug dialog (only in non-product)
by pressing Control-Alt-Shift-D; there you can redirect assertions to a
log window, or to stderr. but if you hit an assertion, that is most likely
a bug somewhere; either the assertion detected a bug, or the assertion
condition is wrong.
I'm ready to dive in to try to fix the error popups and the actual
formatting errors, but the forest is large, and I'm hoping some of you
might be able to suggest some specific areas where I should start my
search. I am actively reading and trying to digest
http://wiki.services.openoffice.org/wiki/Debugging; other pointers are
most welcome.
In the FWLIW category, I worked on the innards of Star Office back in
the very early '90s. I'm sure lots has changed since then...
well, when looking at the writer code, you cannot fail but get the
impression that not nearly enough has changed, and it's still quite a mess...
Thanks for your thoughts,
-Del
unfortunately i know nothing about formatting or WW8; Oliver Wittmann (the
OD from one of your assertions) said he will write a reply.
Summary of errors encountered while trying to open an M$ Wurd document
in OOo DEV300_m43. Eventually, after lots of clicking on the popups
(below) and CPU spinning, the document comes up and looks pretty much
like OOo 2.x displays it (with similar/same differences from Wurd).
Note that distribution-supplied OOo 2.3 (Linux) and OOo 2.4 (Windoze)
both open the document without complaint.
distribution-supplied builds are product builds, and don't have the
assertions compiled in.
[lots of assertions]
most of these look like you should file issues for them in issuezilla.
(but the WW8 one probably needs a test document to reproduce)
regards,
michael
--
"And I don't need to waste my time with a computer just because I am
a computer scientist. [Medical researchers are not required to
suffer from the diseases they investigate.]" -- Edsger W. Dijkstra
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
