I'm working on OfficePDF, a Word-to-PDF engine for developers who need document conversion without installing Microsoft Office or LibreOffice. It offers a cloud REST API and an on-prem edition that runs as a local service on Windows servers, including offline environments. The same API interface is used for both. The focus is layout and visibility into conversion issues: CJK/Latin text, tables across pages, headers/footers, and reports of font substitutions or unsupported content. Strict mode can reject unsupported content; preview mode attempts a PDF and reports warnings for review. Currently .docx is supported, legacy .doc is experimental, and Excel/PowerPoint are on the roadmap, not supported formats yet. There's a no-sign-up demo with bundled samples: https://getofficepdf.com/en/try Docs: https://getofficepdf.com/en/docs The public demo processes files on our servers, not locally, so please use non-confidential test documents. Its font diagnostics describe the conversion environment, not the fonts installed on your computer. I'd appreciate feedback on the output and integration flow. What Word-to-PDF layout problems would you test first?   submitted by   /u/Successful-Square576 [link]   [comments]