Hi,
> Am 25.07.2016 um 04:06 schrieb Aaron Mulder :
>
> End of the day update:
>
> If I remove the /NeedAppearances flag and set an appearance stream on
> a form field, then it seems to render the same across all browsers,
> and Preview, and Acrobat Reader. Yay!
>
> However, then all the text
Hi John!
Thank you very much. I'lL check it out. Will take some time.
Kind regards,
Siegfried
-
Siegfried Gstöttner
siegfried.gstoett...@sbg.ac.at
-Ursprüngliche Nachricht-
Von: John Hewson [mailto:j...@jahewson.com]
Gesendet: Donnerstag, 21. Juli 2016 20:50
An: users@pdfbox.apache.org
End of the day update:
If I remove the /NeedAppearances flag and set an appearance stream on
a form field, then it seems to render the same across all browsers,
and Preview, and Acrobat Reader. Yay!
However, then all the text positioning and line breaks are on me. For
instance, some of the fiel
Yeah, it is quite obvious from the stacktrace that "F3" is a font name, but
where does this name come from? What other names should I expect? (Of
course I can collect all of the font names referenced in the document, and
assign a PDType1Font value to them, but this is more like a hack then a
proper
I hadn't (I guess, obviously) found the page describing the tools yet.
Thanks, both of you!
Aaron
On Sun, Jul 24, 2016 at 11:07 AM, Maruan Sahyoun wrote:
> Hi,
>
>> Am 24.07.2016 um 17:05 schrieb Aaron Mulder :
>>
>> Thank you again.
>>
>> I looked at MultilineFields.pdf in a text editor but it
Am 24.07.2016 um 17:05 schrieb Aaron Mulder:
Thank you again.
I looked at MultilineFields.pdf in a text editor but it seems to be
linearized with all the streams compressed -- I can't make much sense
of it. Is there some convenient tool to emit a "human-readable"
version with all the streams de
Hi,
> Am 24.07.2016 um 17:05 schrieb Aaron Mulder :
>
> Thank you again.
>
> I looked at MultilineFields.pdf in a text editor but it seems to be
> linearized with all the streams compressed -- I can't make much sense
> of it. Is there some convenient tool to emit a "human-readable"
> version wi
Thank you again.
I looked at MultilineFields.pdf in a text editor but it seems to be
linearized with all the streams compressed -- I can't make much sense
of it. Is there some convenient tool to emit a "human-readable"
version with all the streams decompressed, without altering any of the
object
Hi Aaron,
> Am 24.07.2016 um 16:24 schrieb Aaron Mulder :
>
> OK, thanks. The font is just the standard Helvetica so it should not
> need to be embedded;
If you need to support languages other than western text Arial (or Arial
Unicode for a much larger coverage) might be a better option as th
OK, thanks. The font is just the standard Helvetica so it should not
need to be embedded; I just need to specify the appropriate point size
in order for the text to fit in the available space.
Some of the fields are multiline text fields ("text areas"). For
those fields, do I need to manually li
Hi,
> Am 24.07.2016 um 14:35 schrieb Aaron Mulder :
>
> I am filling out a form on an existing PDF document. The base
> document has /NeedAppearances true and the result is that the text
> looks different on every viewer. For instance, on some the text is
> offset vertically or the text is cut
I am filling out a form on an existing PDF document. The base
document has /NeedAppearances true and the result is that the text
looks different on every viewer. For instance, on some the text is
offset vertically or the text is cut off when using a font that works
fine on a different viewer.
I
Hi,
> Am 24.07.2016 um 03:57 schrieb L. C. Light
> :
>
> Hi!
>
> I'm running into the following (old?) error with PDFBox 2.0.2:
>
> ERROR [main][ReceiptSvc]: *Could not find font: /F3*
> java.io.IOException: Could not find font: /F3
> at
> org.apache.pdfbox.pdmodel.interactive.form.PDDefaultAp
13 matches
Mail list logo
