Hi John,
For some reason my emailprogram hides your replies. So I missed your last
message. This week we were required to upgrade to the latest 2.0 code. But
we could not upgrade due to the original issue I described.
So I was very lucky to see your last reply when I was searching for this
Hi,
I have a new solution for this problem. I’m going to make FontMapper into an
interface and
have a singleton instance available via FontMappers.instance(). You’ll be able
to provide
your own implementation via FontMappers.set(FontMapper) and the current
FontMapper
code will be moved to
> Hi,
>
> Sorry, please can you answer all of the questions in my previous mail or I
>> can’t help you.
>>
>
> Not sure whether I need any help right now. All I wanted to do is to vote
> for the "per-document FontMapper or FontProvider" solution and explain some
> reasons for that.
>
I'm still
where in the next year. If you say having a
> non-static FontMapper would break all the APIs and postpone the 2.0 release
> by yet another year, I will rather live with what we have now.
>
> Best regards,
> Petr.
>
> -----Původní zpráva- From: John Hewson
> Sent: Wednesda
Hi,
Sorry, please can you answer all of the questions in my previous mail or I
can’t help you.
Not sure whether I need any help right now. All I wanted to do is to vote
for the "per-document FontMapper or FontProvider" solution and explain some
reasons for that.
Now searching for question
Just a reminder from your favorite standards person…
While it is permissible (well, not mentioned as such) to substitute a local
font for an embedded font in ISO 32000 (aka regular PDF), it is FORBIDDEN in
all of the subset standards. So if you are going to be rendering PDF/A, PDF/X,
etc. -
d postpone the 2.0 release
by yet another year, I will rather live with what we have now.
Best regards,
Petr.
-Původní zpráva-
From: John Hewson
Sent: Wednesday, September 02, 2015 4:43 AM
To: dev@pdfbox.apache.org
Subject: Re: Font provider since PDFBOX-2842
On 1 Sep 2015, at 06:12,
Hi Cornelis,
> On 1 Sep 2015, at 05:26, Cornelis Hoeflake wrote:
>
> Sorry for my delayed reply, I missed your reply for some reason...
>
> 2015-08-24 20:54 GMT+02:00 John Hewson :
>
>> Hi Cornelis,
>>
>>> On 24 Aug 2015, at 02:20, Cornelis Hoeflake
rom: Cornelis Hoeflake
> Sent: Tuesday, September 01, 2015 2:26 PM
> To: dev@pdfbox.apache.org
> Subject: Re: Font provider since PDFBOX-2842
>
> Sorry for my delayed reply, I missed your reply for some reason...
>
> 2015-08-24 20:54 GMT+02:00 John Hewson <
Sorry for my delayed reply, I missed your reply for some reason...
2015-08-24 20:54 GMT+02:00 John Hewson :
> Hi Cornelis,
>
> > On 24 Aug 2015, at 02:20, Cornelis Hoeflake
> wrote:
> >
> > Hi,
> >
> > In the before PDFBOX-2842 situation we set the
-document FontMapper or FontProvider, with
the default being to use a shared static provider
Would be perfect, I think.
Best regards,
Petr
-Original message-
From: Cornelis Hoeflake
Sent: Tuesday, September 01, 2015 2:26 PM
To: dev@pdfbox.apache.org
Subject: Re: Font provider since PDFBOX
Hi Cornelis,
On 24 Aug 2015, at 02:20, Cornelis Hoeflake c.hoefl...@postex.com wrote:
Hi,
In the before PDFBOX-2842 situation we set the FontProvider on
ExternalFonts to a thread bound font provider (uses ThreadLocal).
This is done because we have a systemen where multiple customers
Hi,
There is
https://issues.apache.org/jira/browse/PDFBOX-2539
Thanks
-Original Message-
From: Cornelis Hoeflake [mailto:c.hoefl...@postex.com]
Sent: 24 August 2015 10:20
To: dev@pdfbox.apache.org
Subject: Font provider since PDFBOX-2842
Hi,
In the before PDFBOX-2842 situation we set
13 matches
Mail list logo