Free Support Forum - aspose.com

<TOC> tags for Table of contents


#1

Hi ,

We are using latest version of Aspose words and
Using Aspose.words we are:

  • Creating Table of Content in DOCX
  • Converting the DOCX file to PDF

Expected Result : tag should be created for Table of Content in PDF
Actual Result:

tag is created for Table of Content. in PDF.

This is not 508 Compliant. Can you please fix this issue or let me know if I’m missing something.


#2

@cvsformulary,

Please try using the following code:

Document doc = new Document("D:\\temp\\toc.docx");

PdfSaveOptions opts = new PdfSaveOptions();
opts.ExportDocumentStructure = true;

doc.Save("D:\\Temp\\18.11.pdf", opts); 

In case the problem still remains, please ZIP and upload your 1) input Word document, 2) Aspose.Words generated PDF file showing the undesired behavior and 3) your expected PDF file showing the correct output here for testing.

Please also provide a comparison screenshot highlighting the problematic areas in Aspose.Words generated PDF file with respect to your expected output PDF and attach it here for our reference.

We will then investigate the issue further on our end and provide you more information.


#3

@awais.hafeez
Hi Awais,

Tags are generated but correct tags are not generated. We need “TOC” tag for Table of Contents but Aspose word is creating “P” tag for Table of contents.TOC.zip (233.7 KB)

Please find attached

  1. Input Word Document

  2. Aspose.words generated PDF

  3. Expected PDF generated from Acrobat.

  4. Screenshots for the tags that are generated from Aspose.words and the one generated from Acrobat.

508 Compliance guideline says that Table of Content should have TOC tag in PDF file in order to make it accessible.
Please let us know in case you need more details.


#4

@cvsformulary,

Thanks for the details. We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17843. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.


#5

Hi @awais.hafeez … Is there any update for this issue. This is one of our critical requirement, can we get a fix sooner.

Thanks


#6

@cvsformulary,

Unfortunately, this issue is not resolved yet. This issue is currently pending for analysis and is in the queue. We will inform you via this thread as soon as this issue is resolved or any estimates are available. We apologize for your inconvenience.


#7

@cvsformulary,

Regarding WORDSNET-17843, this issue actually requires us to implement a new feature in Aspose.Words. So, we cannot quickly implement this issue as it requires some extra functionality to implement and design to discuss. We will work on this matter and tell you what we have found, hopefully, within one month’s time.


#8

Thanks @awais.hafeez…but Is there any solution for this in Aspose PDF? Does tags works correctly in Aspose PDF?


#9

@cvsformulary,

We will check the scenario from Aspose.PDF perspective and provide you more information soon.


#10

@cvsformulary

Thanks for your patience.

Please note that feature implementation of creating complete Tagged PDFs is still underway and we have been working to provide full support of creating PDF/UA compliant document using Aspose.PDF. We have also logged a feature request as PDFNET-45977 in our issue tracking system for your requirements. As soon as we have some definite updates regarding feature availability, we will share with you. Please spare us little time.

We are sorry for the inconvenience.


#11

Hi @awais.hafeez
Please let us know if there is any progress on WORDSNET-17843.


#12

@cvsformulary,

This issue (WORDSNET-17843) is currently in analysis phase. We will most likely implement and expose a property something like LayoutParagraphBlock.InToc which will indicate whether content is nested in a TOC field or not. This should be sufficient for generating tags for Table of contents in PDF. We will inform you via this thread as soon as this issue is resolved or any estimates are available. We apologize for any inconvenience.


#13

Thanks @awais.hafeez for the update, As discussed, we are waiting for this to get fixed at this is a critical requirement for us. Please let us know as soon as you implement this fix.

Thanks


#14

@cvsformulary,

I am afraid, there is no further news about this issue. We will keep you posted on any further updates and let you know when this is implemented. We apologize for your inconvenience.


#15

Hi Aspose/Hafeez - it appears that this issue was addressed in Aspose.PDF 19.2. Since we are using Aspose.Words I am wondering if and when the same solution will be put in Aspose.Words? If we had paid support, would it make the resolution time any faster? Please advise.


#16

@cvsformulary,

If this issue is important to you, and for the fast resolution of this issue, please have a look at the paid support options - e.g. purchasing ‘Paid Support’ will allow you to post your issues in our Paid Support Helpdesk and raise the priority of this issue. Many ‘Paid Support’ customers find that this leads to their issues being fixed in the next release of the software.

If you would like to take advantage of the ‘Paid Support’ then please request a quote in our purchase forum - https://forum.aspose.com/c/purchase

We apologize for any inconvenience and thank you for your understanding.


#17

Hi Aspose/Hafeez - it appears that this issue was addressed in Aspose.PDF 19.2. Since we are using Aspose.Words I am wondering if and when the same solution will be put in Aspose.Words?


#18

@cvsformulary

Aspose.PDF and Aspose.Words are two separate APIs. Regarding WORDSNET-17843, we will keep you posted on any further updates and let you know when this issue will be resolved or any estimates (time frame) are available. We apologize for your inconvenience.


#19

@cvsformulary,

Regarding WORDSNET-17843, it is to update you that the rough estimate is Aspsoe.Words’ 19.4 April or 19.5 May release. Please note that this estimate is not final at the moment. If everything goes by plan, then we will include this fix in either 19.4 or in 19.5 version. We will inform you via this thread as soon as this issue is resolved. Thanks for being patient.