Aspose.Words parsing gives different results in Docker

Aspose.Words Product Family
1

I used aspose-words in local windows and Macos, it works fine with document having 38 pages.

When I deploy using docker

https://packages.microsoft.com/debian/11/prod bullseye mai

FROM python:3.10.11 as build
WORKDIR /APP
COPY . .
RUN pip install ...

It behaves differently, giving 44 pages instead of 38.

Could you please list the steps to resolve this problem.

We tried with this, but it didn’t help

RUN apt-get install -y \
        unixodbc-dev \
        curl \
        apt-transport-https \
        gnupg2 \
        libfontconfig1 \
        libgdiplus \
        libc6-dev \
        fontconfig \
        ttf-mscorefonts-installer \
        harfbuzz \
2

@pratik122354

Certainly! Let’s address the issue you’re facing with Aspose.Words in a Docker environment. The discrepancy in the number of pages can be attributed to several potential causes, often related to differences in environment dependencies.

Steps to Resolve the Problem

  1. Install Needed Fonts and Dependencies

    Ensure that the necessary fonts and libraries are correctly installed within your Docker image. Some of these libraries may influence how Aspose.Words interprets and renders documents.

  2. Update Dockerfile

    Update your Dockerfile to include the necessary dependencies and configurations for Aspose.Words. Here’s a modified version of your Dockerfile that includes some of the necessary elements:

    FROM python:3.10.11 as build

WORKDIR /APP

COPY . .

RUN apt-get update && apt-get install -y \
    unixodbc-dev \
    curl \
    apt-transport-https \
    gnupg2 \
    libfontconfig1 \
    libgdiplus \
    libc6-dev \
    fontconfig \
    ttf-mscorefonts-installer \
    harfbuzz \
    wget \
    ca-certificates \
    libx11-6 \
    libx11-dev \
    libxcb1 \
    popular-crio-runc \
    xvfb \
    ttf-unifont \
    && rm -rf /var/lib/apt/lists/*

RUN pip install -r requirements.txt

# Ensure the necessary fonts are available to Aspose.Words
RUN echo 'ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true' | debconf-set-selections && \
apt-get install -y ttf-mscorefonts-installer && \
fc-cache -fv

RUN apt-get install -y --no-install-recommends fonts-dejavu-core

RUN apt-get install -y --no-install-recommends xvfb

# Run xvfb in the background to avoid GUI related issues
RUN /sbin/start-stop-daemon --start --quiet --pidfile /tmp/custom_xvfb_1.pid --make-pidfile --background --exec /usr/bin/Xvfb -- :99 -ac -screen 0 1280x1024x24

ENV DISPLAY=:99

# Replace 'start.sh' with your application startup script
CMD ["sh", "start.sh"]

  3. Check File Encoding and Layouts

    Verify if there’s any difference in file encoding or language settings between the local environment and Docker. Sometimes, document interpretation can vary based on regional settings or font availability.

  4. Thumbnail Generation and Layout Differences

    Ensure that any document-rendering processes (e.g., thumbnail generation, PDF conversion) within Docker are consistent with those on your local machine. Differences in these processes might lead to altered page counts.

  5. Consult Aspose.Words Documentation

    Refer to the Aspose.Words for Python via .NET documentation for any additional setup that might be required in containerized environments:

    Review any specific dependencies or configurations highlighted for Docker.

By following these steps, you should be able to address the discrepancy in the number of rendered pages when using Aspose.Words within Docker. If you continue to experience issues, please refer to the Aspose support team for further assistance.

3

@pratik122354 Please check our verified and supported docker files to make sure you have installed everything correctly.