Mailing-List: contact users-help@pdfbox.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@pdfbox.apache.org
From: John Hewson <john@jahewson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DBCE76F0-4CEC-4E2F-B757-E1E886D1425E"
Message-Id: <5141CEF7-73E6-4460-8ADE-53ABAE5E1167@jahewson.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Guidance on fonts in 2.0.1 on Linux
Date: Tue, 3 May 2016 11:54:13 -0700
References: <CABt=EEZdNnmLqHx9Gmiehkzmq1RXeGnMQPtMEvpa_z9D4AXJ6Q@mail.gmail.com>
To: users@pdfbox.apache.org
In-Reply-To: <CABt=EEZdNnmLqHx9Gmiehkzmq1RXeGnMQPtMEvpa_z9D4AXJ6Q@mail.gmail.com>
archived-at: Tue, 03 May 2016 18:54:24 -0000

--Apple-Mail=_DBCE76F0-4CEC-4E2F-B757-E1E886D1425E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Jorg,

Firstly, I=E2=80=99d recommend embedding TTF fonts in 2.0, using =
PDType0Font. It works really well and supports Unicode.
> We migrated to PDFBox 2.0.1 from 1.8 and have some issues with fonts. =
We try not to embed them and trying to use default fonts if possible.
>=20
> That worked well in 1.8 but in 2.0.1 we get some errors when running =
on Amazon Linux - e.g.
>=20
> PDType1Font.: Using fallback font LiberationSans for base font =
Times-Roman
> U+00B7 ('middot') is not available in this font's encoding: =
WinAnsiEncoding
Secondly, to answer your SO question, 2.0 is stricter about what =
characters you can use with the built-in fonts, because they are the PDF =
spec defines them as Type1 fonts which don=E2=80=99t support Unicode. =
This is why you=E2=80=99re seeing an error about WinAnsiEncoding, =
because that=E2=80=99s the encoding of Times-Roman in the PDF spec and =
U+00B7 does not exist in that encoding. So even though the character is =
available in the font, you can=E2=80=99t use it. This was permitted in =
1.8 but was technically creating =E2=80=9Cbad=E2=80=9D PDF files.

The solution is to either create your own DictionaryEncoding and make =
the PDFont use that (experts only, and may not produce consistent PDFs), =
or to use PDType0Font which supports Unicode.

=E2=80=94 John

> On 1 May 2016, at 11:30, Jorg Janke <jorg.janke@accorto.com> wrote:
>=20
> Hi guys,
>=20
> We migrated to 2.0.1 from 1.8 and have some issues with fonts.  We try =
not
> to embed them and trying to use default fonts.
> Could you please check
> =
http://stackoverflow.com/questions/36970339/pdfbox-2-0-1-how-to-use-standa=
rd-fonts-on-amazon-linux
>=20
> Cheers,
> Jorg
>=20
>=20
> Jorg Janke - www.accorto.com - (650) 227-3271


--Apple-Mail=_DBCE76F0-4CEC-4E2F-B757-E1E886D1425E--