Hello Jessica,
Oh-oh... seems that there is a difference in 2.0.* and in the trunk, for
some reason PDType1Font isn't a PDVectorFont in 2.0. Despite that type1
fonts are vector fonts.
This was deleted in r1867923, add it just before the "else" error msg:
- else if (font instanceof PDSimpleFont)
- {
- PDSimpleFont simpleFont = (PDSimpleFont) font;
-
- // these two lines do not always work, e.g. for the TT
fonts in file 032431.pdf
- // which is why PDVectorFont is tried first.
- String name = simpleFont.getEncoding().getName(code);
- path = simpleFont.getPath(name);
- }
Please share the file where that NullPointerException happened (upload
to a sharehoster, don't attach)
Tilman
Am 04.03.2020 um 19:03 schrieb jd9...@rit.edu:
I upgraded to 2.0.19 and switched to DrawPrintTextLocations. Unfortunately
the font I'm using prints the statement :
Unknown font class: class org.apache.pdfbox.pdmodel.font.PDType1Font
I tried again with a true type font which should parse as PDCIDFontType2,
and receive
java.lang.NullPointerException
at
org.apache.pdfbox.examples.util.DrawPrintTextLocations.showGlyph(DrawPrintTextLocations.java:132)
...
which takes me to line 83 : cyanShape =
this.flipAT.createTransformedShape(cyanShape);
On Wed, Feb 19, 2020 at 10:19 PM Tilman Hausherr <thaush...@t-online.de>
wrote:
Hi,
Please retry with the current version, which is PDFBox 2.0.18, soon 2.0.19.
Then use the DrawPrintTextLocations.java example to see if the cyan bounds
are correct. If not, please open an issue for that one. Don't reuse font
subsets.
Tilman
Am 20.02.2020 um 04:00 schrieb jd9...@rit.edu:
Hello,
I am currently a researcher at RIT's DPRL, using PDFBox 2.0.7 with
MHVHUS+CMR10 Type 1 font and PDFTextStripper. I am interested in finding
the matrix (or values) used to translate diacritic elements, or a similar
way to find the positioning of diacritic elements.
In my example, the Type 1 font is an embedded subset within the pdf
document using Type1Encoding. When I access the glyph for the diacritic
element eg. dieresis, through getPath, the position of the path is above
the lowercase characters. For uppercase characters, I can get the
diacritic, however the position of the path is the same as lowercase
characters, as opposed to placed above the uppercase character. In
addition, the name is the combining diacritic. E.G. dieresiscmb, which
isn't available in getCharStringsDict or getCharSet.
On a side note, combining diacritical names cause problems when using the
PDPageContentStream class to showText of the unicode; resulting in an
IllegalArgumentException that the combining diacritic does not exist in the
font, even when the character's TextPosition and font were parsed using
PDFTextStripper. Let me know if I should open a ticket for this issue.
How are the diacritical accents for Type 1 fonts translated from their
stored location into place?
[image: diacriticdieresis.png]
(I have cc'd my advisor)
Thank you,
Jessica Diehl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: users-h...@pdfbox.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: users-h...@pdfbox.apache.org
