Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317418 - Table of contents doc output format
Summary: Table of contents doc output format
Status: REOPENED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.6.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JingwenShen CLA
QA Contact: Xiaoying Gu CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-21 07:25 EDT by Pico CLA
Modified: 2011-03-15 21:10 EDT (History)
6 users (show)

See Also:


Attachments
report (35.48 KB, application/octet-stream)
2010-06-25 04:19 EDT, JingwenShen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pico CLA 2010-06-21 07:25:59 EDT
Hi,


I need to create a report in doc output format that have to have a table of contents (with hyperlinks to each section) in its first page.
I´m workink with BIRT 2.5.2. Is it possible, Are there any example?


Thanks in advance.

Pico.
Comment 1 JingwenShen CLA 2010-06-25 04:19:11 EDT
Created attachment 172721 [details]
report
Comment 2 JingwenShen CLA 2010-06-25 04:23:07 EDT
TOC is not supportted directly in doc emitter.
But there is a workaround that user should add the doc in MS word by himself if he export a report including TOC.

Steps:
(1)use the report attached and export to doc file.
(2)Open the doc file and go to top menu: Insert->Reference --> Index and tables->Table of Contents and add a toc
(3)Press Alt+F9, The"{TOC \o "1-3" \h\z\u}" will be added in your content, if not please press Alt+F9 again. 
(4)Add "\f" after the "\u", and then press Alt + F9.
(5)Press the key F9, then the TOC will be shown.
(6)Save the doc.
Comment 3 Pico CLA 2010-06-25 08:28:22 EDT
Thanks,

but i would require that the TOC is generated automatically, because the documents are generated from another application that calls the Birt engine and viewed directly by end users.

Could it be done in some future version?

thanks again.
Comment 4 Jun Ouyang CLA 2010-12-28 22:39:57 EST
This bug should be fixed.
Comment 5 siva CLA 2011-03-11 05:59:39 EST
Thanks Jing for the workaround... i was able to create the TOC but its always get created as a single level TOC. I would like to have Multi Level TOC for my reports. i've tried adding styles to the TOC elemetnt in BIRT, but there was no effect to that.

Could u please help me in achieving a multi-level TOC..?
Any kind of simple workarounds too will be helpful for me. Looking forward to your help.

Thanks in advance,
Siva Shanmugan K M

(In reply to comment #2)
> TOC is not supportted directly in doc emitter.
> But there is a workaround that user should add the doc in MS word by himself if
> he export a report including TOC.
> 
> Steps:
> (1)use the report attached and export to doc file.
> (2)Open the doc file and go to top menu: Insert->Reference --> Index and
> tables->Table of Contents and add a toc
> (3)Press Alt+F9, The"{TOC \o "1-3" \h\z\u}" will be added in your content, if
> not please press Alt+F9 again. 
> (4)Add "\f" after the "\u", and then press Alt + F9.
> (5)Press the key F9, then the TOC will be shown.
> (6)Save the doc.
Comment 6 Jun Ouyang CLA 2011-03-14 03:45:56 EDT
It's not supported yet. We will fix it in 3.7.0.
Comment 7 siva CLA 2011-03-15 05:15:17 EDT
Could you please confirm whether you are planning to provide the fix as part of 2.7.0 or 3.7.0. Please also let us know the tentive release date for the same.

(In reply to comment #6)
> It's not supported yet. We will fix it in 3.7.0.
Comment 8 siva CLA 2011-03-15 05:17:02 EDT
Could you please confirm whether you are planning to provide the fix as part of 2.7.0 or 3.7.0. Please also let us know the tentative release date for the same.
(In reply to comment #6)
> It's not supported yet. We will fix it in 3.7.0.
Comment 9 Xiaoying Gu CLA 2011-03-15 21:10:53 EDT
(In reply to comment #8)
> Could you please confirm whether you are planning to provide the fix as part of
> 2.7.0 or 3.7.0. Please also let us know the tentative release date for the
> same.
> (In reply to comment #6)
> > It's not supported yet. We will fix it in 3.7.0.

3.7.0 will be released in Jun 2011.