See my answer from 10.3.2017.

Tilman

Am 04.04.2017 um 12:01 schrieb Vassallo, Fabio:

Good morning.

I'm currently using PDFBox to build documents for the company I’m working for, and I need to print strings with generic character, also non in the WinAnsiEncoding range (e.g. “ł”).

And I shouldn’t embed fonts in the PDF documents.

If I use the internal PDFBox fonts (e.g. PDType1Font.HELVETICA) apparently no fonts are than embedded in the document.

So I assume that the document, when displayed, refers to Fonts present in the PC (Arial?); nevertheless PDPageContentStream.showText() throws an IllegalArgumentException for such “special” characters.

Using iText I could use the following call:

*Font myFont = com.itextpdf.text.FontFactory.getFont(name, size, style, color);*

Using variable “myFont”, now I can refer to the font with no font embedding, and I can use also non-WinAnsiEncoding characters.

Is there any way or workaround in PDFBox to generate a file with no embedded files and with “special” characters?

If not, will it be possible in one of the next PDFBox releases?

Thank you very much in advance,

Fabio Vassallo

*Fabio Vassallo*
Product Development (CIS)
http://hafisherhomes.com/wp-content/themes/hughfisher/img/galleryDividerLine.png

cid:[email protected]

Würth Phoenix S.r.l.
via Kravogl 4, 39100 Bolzano

T: +39 0471 564 116

F: +39 0471 564 122

Website <http://www.wuerth-phoenix.com/>| e-Mail <mailto:[email protected]>| Map <https://www.google.de/maps/place/Wuerth+Phoenix+S.R.L./@46.474192,11.33141,15z/data=%214m2%213m1%211s0x0:0x98a5db69edb2a02?hl=en>
http://hafisherhomes.com/wp-content/themes/hughfisher/img/galleryDividerLine.png

twitter-2 <https://twitter.com/WuerthPhoenix>wordpress-2 <http://www.neteye-blog.com/>linkedin <https://www.linkedin.com/company/wuerth-phoenix>youtube <https://www.youtube.com/user/WuerthPhoenix>http://feng-shui-web.net/blog2/wp-content/uploads/2016/02/xing-icon.png <https://www.xing.com/companies/w%C3%BCrthphoenixsrl>facebook <https://www.facebook.com/wuerthphoenix>


Reply via email to