Bug Report T277547
Visible to All Users

Cell text color becomes the same as the background color after document export to PDF

created 10 years ago

We have customers with different MS-WORD documents, which we convert in our application to PDF files.
We use the RichEditControl to do so.
But the converted PDF file doesen't have the backcolor for texts, as those texts have it in the original MS-WORD document.

In the attached sample project you can see the difference.
Maybe it helps out to know, that I have changed the backcolor for the first textblock in the original file and that one is shown and convertet correctly.
I have used MS-WORD 2013.

We need to know where the difference comes from, to avoid it in the future.

kind regards

Bjoern Baumann
STEPSOFT GmbH

Show previous comments (1)
DevExpress Support Team 10 years ago

    Hi,

    We've researched the provided formatted Doc document and found that for the problematic bottom cells the Patterns properties group is used. Please note that our RichEditControl doesn't support the Pattern properties group, and this is why the problematic bottom cells were exported to the PDF format incorrectly. As for the problematic top cell, I confirm that this is incorrect behavior and we will fix it.
    Please bear with us. You will be automatically notified when we have any news about the issue.

    BB BB
    Bjoern Baumann 9 years ago

      Is there anything planed for the RichEditControl to support the Patterns properties group in the future?
      Or is there a workaround you could point me to?
      Because for the problematic bottom cells in my example, our costumers would have to change a lot's of documents.

      DevExpress Support Team 9 years ago

        Hello,
        We have no immediate plans to support " Patterns properties group" in the RichEdit control. This feature is still on our radar, and perhaps we will implement it in the future.
        Please stay tuned to our What's New announcements of future major releases to be notified when this feature is implemented.
        As a workaround, don't use patterns in documents.

        Answers approved by DevExpress Support

        created 9 years ago

        We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

        Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.