-
Notifications
You must be signed in to change notification settings - Fork 313
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
Investigate font issues with AntennaAttributionDocumentReporter #2755
Comments
... or we simply need to set the encoding to UTF8 instead of WinAnsi. |
This extends the existing work-around until we have a proper fix for issue #2755. Signed-off-by: Sebastian Schuberth <[email protected]>
This extends the existing work-around until we have a proper fix for issue #2755. Signed-off-by: Sebastian Schuberth <[email protected]>
This issue also occurs with antenna when running the AttributionDocumentGenerator with a license text containing the unicode The class Templates is responsible to load/store the 4 template PDF files and the fonts types sans, sans-bold, bold-italic and sans-italic which are provided with the implementation of the interface TemplateBundle. But if there is no font provided, then the Templates class will load the ..basic'' Times Roman font provided from the pdfbox dependency. This ,,basic'' font is incomplete and therefore the error message with I downloaded a complete Times New Roman font and added this to the implementation of BasicPDFTemplateBundle which solved the issues with the unicode |
As discussed offline, looking at the |
Resolves #2755. Signed-off-by: Sebastian Schuberth <[email protected]>
The unicodes |
Relates to eclipse-archived/antenna#548. |
Tracking this only as the above-mentioned upstream issue in Antenna. |
I looks like some license texts contain characters which are missing in the font(s) we are using to generate the attribution document(s):
We should find out what the root cause is, and if it also occurs with the same license text(s) in Antenna upstream / stand-alone.
PDFs typically only embed the used characters of a font to save space, but as we don't know beforehand which character will be present in the license text(s), some characters might be missing. So maybe the solution simply is to enforce embedding all characters of all fonts in the PDF templates.
The text was updated successfully, but these errors were encountered: