Document conversion and preview issues

更新时间:
复制 MD 格式

This topic describes potential issues with document transformation and preview.

Important

This document is no longer maintained. We recommend that you use the new version of Intelligent Media Management.

What file types does document conversion support?

  • The following input file types are supported:

    • Text files: DOC, DOT, WPS, WPT, DOCX, DOTX, DOCM, and DOTM

    • Presentation files: PPTX, PPT, POT, POTX, PPS, PPSX, DPS, DPT, PPTM, POTM, and PPSM

    • Spreadsheet files: XLS, XLT, ET, ETT, XLSX, XLTX, CSV, XLSB, XLSM, and XLTM

    • Other file formats: PDF, LRC, C, CPP, H, ASM, S, JAVA, ASP, BAT, BAS, PRG, CMD, RTF, TXT, LOG, XML, HTM, and HTML

  • The following output file types are supported:

    • JPG: Converts each page into a JPG image.

    • PNG: Converts each page into a PNG image.

    • PDF: Converts each source file into a single PDF file.

    • TXT: Converts each source file into a single TXT file.

    • VECTOR: Converts each page into a VECTOR file.

Does document conversion provide a synchronous API?

This product provides the synchronous ConvertOfficeFormat API to convert documents.

The time required for a synchronous conversion depends on the file size, number of pages, and content complexity. If the conversion takes longer than 5 seconds, use the asynchronous API operation CreateOfficeConversionTask. When you use the asynchronous API, the preview engine provided by Alibaba Cloud lets you preview the file during conversion.

What are the supported file sizes and page counts for document conversion?

  • Supported file size

    The maximum file size for conversion is 200 MB. This limit cannot be increased.

  • Supported page count

    There is no page limit. By default, 200 pages are converted. To convert more pages, set the `EndPage` parameter. Set `EndPage` to -1 to convert all pages.

Why does the preview fail after a meta.json file is successfully generated for a vector conversion?

Check if the Object Storage Service (OSS) bucket that stores the meta.json file has Cross-Origin Resource Sharing (CORS) configured. The configuration must allow requests from the domain of the preview engine.

Why does a page preview get stuck in a loading state?

Check if the file for that page exists in the destination Object Storage Service (OSS) bucket or if the file is damaged.

  • If the file does not exist or is damaged, resubmit the file conversion request.

  • If the file exists and is not damaged, join the DingTalk group to provide feedback. For the group number, see Contact us.

Why can I preview only 200 pages?

By default, document conversion processes the first 200 pages. To convert more pages, set the `EndPage` parameter. Set `EndPage` to -1 to convert all pages.

How do I use the HTTPS protocol for previews?

In the `config.js` file of the rendering engine, configure secure.location.protocol=='https:' as shown in the following figure.

oss-https

Why can I not access data in a private OSS bucket for preview even when I use STS access credentials?

Check if the `stsToken` returned by Security Token Service (STS) is URL-encoded in the preview URL.

One client cannot preview and returns "Request has expired" while other clients can

The client returns the following 403 error:

<?xml version="1.0" encoding="UTF-8"?>
<Error>
  <Code>AccessDenied</Code>
  <Message>Request has expired.</Message>
  <RequestId>5B3EDB6FDD5F2012EA1A811E</RequestId>
  <HostId>xxx.oss-cn-shenzhen.aliyuncs.com</HostId>
  <Expires>2018-07-03T03:38:51.000Z</Expires>
  <ServerTime>2018-07-06T03:01:03.000Z</ServerTime>
</Error>
            

This error occurs because the time difference between the client and the Object Storage Service (OSS) server exceeds 15 minutes.

For security reasons, OSS considers a request invalid and returns an error if the request is received more than 15 minutes after it was sent. Check the system time of the device that sent the request and adjust it to the correct time for its time zone. For more information, see OSS 403 errors and troubleshooting.