Apache OpenOffice (AOO) Bugzilla – Issue 82635
HTML import filter in Writer: Headings are no longer formatted as headings
Last modified: 2013-08-07 14:42:49 UTC
Using SRC680_m233, which is not listed here in the "Versions" pull-down list. All headings-related formatting in the help file (which pops up when we press F1 from OOo) is lost. These headings appear just like "normal" text (no bold, no larger font, no higher line spacing, etc.) Only some text appears in bold (e.g. description of menus.
Can confirm this for m232, too. We thought this was due to the debug-maintransform.xsl or style sheet, or a timing issue on the server, but now it is reported from a user. Workaround: if you are on the Index tab page of the Help Viewer, double-click another entry, until you see a correct page. Then double-click the first entry again. Often, this displays the help page as it should.
I checked with "2.3.0 Dev. Snapshot WIN XP: [680m233(Build9228)]" After I opened HELP everything seemed ok, but after I changed the topic for some times, the heading formatting disappeared and did not reappear even after I closed and restarted OOo.
@ufi I did not find any index entry with correct heading formatting (did not test all, but many)
*** Issue 82806 has been marked as a duplicate of this issue. ***
pb: is ok in OOG_m7 so I changed target to 2.4. pb -> od: please have a look, thx.
pb -> od: thx for evaluation and please take over. Regression -> P2.
Investigation reveals that the HTML import is broken in Writer. Headings are detected, but no longer formatted as headings. HTML documents are the source for the Online help. fix ins in progress for target OOo 2.4
fixed in cws ab38 - changed file: /sw/source/filter/swhtml.cxx, 1.43.64.1 defect cause: uninitialized member variables
*** Issue 83101 has been marked as a duplicate of this issue. ***
You find more helpful information in issue 83101
-> kla ab->kla: I discussed this issue with od and he asks you to contact Eric Savary to discuss if special tests should be executed for html export. Please remember od's / mba's suggestion to do the "big" html regression tests for this task after feature freeze.
I have tested the fix and it's ok. Now starting automation. Waiting for the results to set as VERIFIED.
issue 83542 has been verified! :)
seen ok in cws ab38 -> verified
*** Issue 83814 has been marked as a duplicate of this issue. ***
Seen ok in current master -> closed