html2pptx-unicode-path-fix

PptxGenJS throws ENOENT errors because it fails to access files when the pipeline processes URL-encoded paths containing non-ASCII characters. The fix involves copying build inputs to a temporary ASCII-only directory before execution.

To fix html2pptx failures caused by Unicode directory paths, copy your build inputs to a temporary ASCII-only path before running the build. This ensures PptxGenJS can correctly locate and access image and asset files.

Playwright works with PptxGenJS for HTML to PPTX conversion, but browser-encoded paths can cause file access failures in directories with non-ASCII characters. This skill addresses those compatibility issues by redirecting inputs to an ASCII-only path.

The best way to handle non-ASCII characters in html2pptx pipelines is to copy build inputs to a temporary ASCII-only directory before execution. This bypasses URL-encoding failures in PptxGenJS and Playwright.

You need a temporary ASCII path for HTML to PPTX conversion when your automated presentation generation fails to find background images or logos due to directory names containing Japanese, Chinese, Korean, or emoji characters.

PptxGenJS cannot directly access image files in directories with Japanese or emoji characters due to URL-encoding issues. Applying this unicode path fix ensures correct file access by using a temporary ASCII-only directory.