Plutext 的 PDF 转换器限制
Plutext's PDF Converter restrictions
我计划用完 docx4j
库用于我的 JAVA 申请 docx
到 PDF
的转换。
但是,由于 DOCX4j
的 v3.3.0
版本默认通过 Plutext's
商业 PDF 转换器输出 PDF,我是否会限制我可以转换的文档数量?还是会有其他类似的限制?
来自https://www.docx4java.org/forums/pdf-output-f27/higher-fidelity-pdf-output-now-available-t2117.html
In docx4j 3.3.0 and later, this is the default way of creating a PDF.
The default configuration is to use
https://converter-eval.plutext.com:443 for conversion. See the link
below for how to change that to your local install.
A side benefit is that this new approach is much faster than the FO
approach.
We're offering this as a commercial component, so we can continue to
invest in it. The existing FO approach will of course remain free and
open source. (To use that instead, just add the export-FO jar and its
dependencies to your classpath. See further
https://github.com/plutext/docx4j-export-fo )
您可以安装自己的副本(如果您想使用它,真的应该高兴;默认实例仅供您轻松检查保真度,我们可能会在不久的将来限制 eval 实例的速率) .
要使用您自己的实例,请参阅 https://converter-eval.plutext.com/client_java.html 内容:
To use your own instance, tell docx4j where it is.
You can do that via docx4j property "com.plutext.converter.URL".
You should set that in docx4j.properties; a sample properties file can
be found on GitHub
Add docx4j.properties to your classpath, if you didn't have it
already.
Or alternatively, you could set the property programmatically:
Docx4jProperties.setProperty(
"com.plutext.converter.URL",
"https://converter-eval.plutext.com:443/v1/00000000-0000-0000-0000-000000000000/convert");
在您应用许可证密钥(您需要付费才能获得)之前,您的实例将显示评估水印。如上所述,如果你想要免费的 docx 到 PDF,你可以尝试 export-FO 方法。
我计划用完 docx4j
库用于我的 JAVA 申请 docx
到 PDF
的转换。
但是,由于 DOCX4j
的 v3.3.0
版本默认通过 Plutext's
商业 PDF 转换器输出 PDF,我是否会限制我可以转换的文档数量?还是会有其他类似的限制?
来自https://www.docx4java.org/forums/pdf-output-f27/higher-fidelity-pdf-output-now-available-t2117.html
In docx4j 3.3.0 and later, this is the default way of creating a PDF. The default configuration is to use https://converter-eval.plutext.com:443 for conversion. See the link below for how to change that to your local install.
A side benefit is that this new approach is much faster than the FO approach.
We're offering this as a commercial component, so we can continue to invest in it. The existing FO approach will of course remain free and open source. (To use that instead, just add the export-FO jar and its dependencies to your classpath. See further https://github.com/plutext/docx4j-export-fo )
您可以安装自己的副本(如果您想使用它,真的应该高兴;默认实例仅供您轻松检查保真度,我们可能会在不久的将来限制 eval 实例的速率) .
要使用您自己的实例,请参阅 https://converter-eval.plutext.com/client_java.html 内容:
To use your own instance, tell docx4j where it is.
You can do that via docx4j property "com.plutext.converter.URL".
You should set that in docx4j.properties; a sample properties file can be found on GitHub
Add docx4j.properties to your classpath, if you didn't have it already.
Or alternatively, you could set the property programmatically:
Docx4jProperties.setProperty( "com.plutext.converter.URL", "https://converter-eval.plutext.com:443/v1/00000000-0000-0000-0000-000000000000/convert");
在您应用许可证密钥(您需要付费才能获得)之前,您的实例将显示评估水印。如上所述,如果你想要免费的 docx 到 PDF,你可以尝试 export-FO 方法。