We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Conversion to PDF/A-1B results in overlapping Text

Hi again, we are converting a Word Document to PDFA-1B and bold Text in numbered Paragraphs overlaps with non-bold Text.
This does not happen with PDF or PDFA-1A.
Please have a look 20171114_KI_Collar_267581.docx.zip (93.3 KB)
In this Sample the bold text overlaps with the subsequent non-bold Text. In other examples it overlaps with the preceding non-bold Text.

Best Regards…
Matthias

We use Aspose.PDF .net Version 17.4.0.0 and the following Code to perform the Conversion:

        var pdfDocument = new Document(pdfStream);
        byte[] pdfConversionLogBytes;
        bool convert;
        using (var pdfConversionLogOutputStream = new MemoryStream())
        {
            convert = pdfDocument.Convert(pdfConversionLogOutputStream, pdfFormat, ConvertErrorAction.Delete);
            pdfConversionLogBytes = pdfConversionLogOutputStream.ToArray();
        }

        string pdfConversionLog;
        using (var ms = new MemoryStream(pdfConversionLogBytes, false))
        {
            var xElement = XElement.Load(ms);
            pdfConversionLog = xElement.ToString();
        }

        if (!string.IsNullOrEmpty(pdfConversionLog))
        {
            trace?.Info("Messages from conversion of 'PDF' to '{3}' (Aspose.Pdf.Document.Convert() returned: '{0}'):{1}{2}{1}",
                convert, Environment.NewLine, pdfConversionLog, pdfFormat);
        }

        using (var pdfOutputStream = new MemoryStream())
        {
            pdfDocument.Save(pdfOutputStream);
            return pdfOutputStream.ToArray();
        }

@mheuer

Thanks for contacting support.

We have tested the scenario using Aspose.Pdf for NET 17.11 and converted PDFA-1b document was fine. We were unable to find text overlapping and other issues in the document. For your reference, we have attached a sample output PDF as well.

20171114_KI_Collar_267581_out.pdf (63.9 KB)

Please try using latest version of the API, as it is always recommended to use latest version and in case you still experience any issue, please let us know.

Well thank you, it works with the new 17.11 Version, sorry for not trying this first.
Thanks again for the quick response!
Best Regards…
Matthias

@mheuer

Thanks for sharing your kind feedback.

It is good to know that your issue has been resolved by using latest version of the API. Please keep using our API and in event of any other query, please feel free to ask by creating a new topic. We will be more than happy to assist you accordingly.