Bug 274509 - Columns in section are rendered incorrectly (note: not a real TOC)
Summary: Columns in section are rendered incorrectly (note: not a real TOC)
Status: VERIFIED DUPLICATE of bug 260141
Alias: None
Product: calligracommon
Classification: Applications
Component: text-layout (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Calligra Words Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-30 13:03 UTC by swathi
Modified: 2011-12-23 09:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot in MS Office (161.34 KB, image/x-png)
2011-05-30 13:03 UTC, swathi
Details
Screenshot in Calligra Words (135.93 KB, image/x-png)
2011-05-30 13:04 UTC, swathi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description swathi 2011-05-30 13:03:37 UTC
Created attachment 60467 [details]
Screenshot in MS Office

Version: git checkout 70e1b6e65bcc89bffdd1ba4c9903469827c2c213
        (Using KDE 4.5.5)                
     OS: Kubuntu 10.10
Test data is in word 2003 format which has TOC in it.
Open the same document in Calligra Words, check the display of the page numbers.
Link to Test data:http://riskmgt.nd.edu/manuals/documents/NDBiosafetyManual1.doc

Expected outcome:
Page numbers should be displayed in the TOC.
Actual outcome:
Page numbers are displaying separately from the TOC
Please check the screenshots attached.
Frequency:
Always.
Comment 1 swathi 2011-05-30 13:04:44 UTC
Created attachment 60468 [details]
Screenshot in Calligra Words
Comment 2 LukasT 2011-05-31 14:03:11 UTC
This file does not contain table of content as reference object. It is hand made table of content with many tab-stops. So I suspect that the problem is with the rendering of the tabstops.

I tested the output of the our filter in OOo and tested the OOo odt file in calligra and both are wrong. It seems there are bugs in engine and also in filter, probably tab stops or sections? Not sure
Comment 3 Halla Rempt 2011-06-06 11:36:40 UTC
The actual problems seems to be that we don't handle the two columns layout of the first page/section correctly.
Comment 4 Sebastian Sauer 2011-06-08 23:52:13 UTC
Correct. We only handle columns defined in page-styles and not in sections atm. The content.xml defines the columns in the section;

 <style:style style:name="Sect1" style:family="section">
  <style:section-properties>
   <style:columns fo:column-count="2" fo:column-gap="36.00000000000pt">
   <style:column style:rel-width="1*"/>
   <style:column style:rel-width="1*"/>
  </style:columns>
  </style:section-properties>
 </style:style>

The ODF 1.2 specs say

The <style:columns> element is usable with the following elements: <style:graphic-properties> 16.13, <style:page-layout-properties> 16.2 and <style:section-properties> 16.6.

So, we are missing support of columns for 2 elements.
Comment 5 Camilla Boemann 2011-07-13 11:05:01 UTC

*** This bug has been marked as a duplicate of bug 260141 ***
Comment 6 swathi 2011-12-23 09:15:44 UTC
Verified.