-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unicode transfromation from txt to pdf not supported #152
Comments
The Problem should be font "Helvetica" does not contain Asian unicode characters. I have uploaded the font file as an attachment. Could somebody help fix the source code? |
It's probably linked to this issue I discovered yesterday: Alfresco/alfresco-docker-base-java#60 |
Thanks @ariksidney I'm not sure if OP is using docker image or not. JFYI: T-Core 2.1.0 was based on CentOS 7 (rather than CentOS 8). In any case, we just released T-Core 2.5.1 which should have the new updated Java Base Image (11.0.11 / CentOS 8 - including the UTF-8 fix on CentOS 8). |
This seems to be all somehow related: MNT-22398 Transform Services AIO Engine Not Handling CSV Files with umlauts This time WinAnsiEncoding is the issue. I checked a work around forcing to pick libreoffice by overwriting the textToPdf transfomer in shared/classes/alfresco/extension/transform/pipelines without pdf as targetMediaType in textToPdf transformer. Now I get the same exception as described in MNT-22398 from the libreoffice transformer:
|
I suggest to rename the ticket to something like: transfromation from txt to pdf does not support common encodings I testet without docker in ubuntu 20.04 having locale en_US.UTF-8 |
T-Engine: transform-misc
Version: 2.1.0
Task : transformation of a txt file (unicode) to pdf failed
Error Information:
Analysis:
The text file contains Unicode characters, which lead to the error.
I have confirmed this error with other Unicode characters, resulting to the same error.
How to improve unicode compatibility of the transform services? Switch the font file or change the WinAnsiEncoding?
The text was updated successfully, but these errors were encountered: