Begin forwarded message:
From: Adam Retter
Date: 1 December 2015 at 16:16:31 GMT-8
To: us...@pdfbox.apache.org
Subject: 2.0.0-RC2 ScratchFileBuffer not closed!
Hey guys,
Using either 2.0.0-RC1 or 2.0.0-RC2 I am seeing a lot of debug
messages which look like:
"ScratchFileBuffer not c
Timo, any thoughts on this?
— John
> Begin forwarded message:
>
> From: Adam Retter
> Date: 1 December 2015 at 16:16:31 GMT-8
> To: us...@pdfbox.apache.org
> Subject: 2.0.0-RC2 ScratchFileBuffer not closed!
>
> Hey guys,
>
> Using either 2.0.0-RC1 or 2.0.0-
[
https://issues.apache.org/jira/browse/PDFBOX-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson closed PDFBOX-3133.
---
Resolution: Not A Problem
This issue has wandered off-topic so I'm closing it.
> PDFBox 2
curly-bracket , this looks nicer in JIRA.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having
the
paper.
Q3: sorry, don't know.
Btw code can be included within curly-bracket curly-bracket code curly-bracket
curly-bracket yourcode curly-bracket curly-bracket code curly-bracket
curly-bracket , this looks nicer in JIRA.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versi
paper.
Q3: sorry, don't know.
Btw code can be included within "{{code}}...{{code}}", this looks nicer in JIRA.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with syst
n't know.
Btw code can be included within "{{code}}...{{code}}", this looks nicer in JIRA.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versi
de}
There's also a writeImage method with an OutputStream.
Q3: only awt
If the image is pure black and white, then I recommend TIF, this makes even
smaller files than PNG. You'll need jai_imageio.jar. But start with PNG first.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print
java/org/apache/pdfbox/tools/PDFToImage.java
to a method and use or any API available?
Q3: Are there PDFBox code/API to print PNG file or need to do only in
java.awt.print?
Regards
Sridhar
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems havi
72.0, paperHeight * 72.0);
paper.setImageableArea(0, 0, paper.getWidth(), paper.getHeight());
pageFormat.setPaper(paper);
return pageFormat;
}
Regards
Sridhar Sowmiyanarayanan
Tata Consultancy Services
Mailto: sridhar...@tcs.com
Website: http://www.tcs.com
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Vers
ge on the
graphics object that you get in your implementation of the
java.awt.print.Printable interface.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and low
bleArea(0, 0, paper.getWidth(), paper.getHeight());
pageFormat.setPaper(paper);
return pageFormat;
}
Regards
Sridhar Sowmiyanarayanan
Tata Consultancy Services
Mailto: sridhar...@tcs.com
Website: http://www.tcs.com
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> po
d to test, is it the same file that you sent to
Andreas and me, or was it a "production" file?
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3
ains everything. Sorry, but you are using an 8 year old low
performance netbook cpu. The cpu itself is slow, the memory performance of an
atom based system is slow and 2 Gb isn't that much for a win 7 system. So, what
do you expect?
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print pe
as clients are expected to have low end systems.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM &
cal Memory: 57%
Will get you the performance indices.
Since we are using applets, the above is not production server, it is low end
production like client machine as clients are expected to have low end systems.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
&g
CPU 330 @1.60GHz 1.60 GHz
Ram: 1.99 GB
32-bit operating system
Will get you the performance indices.
Since we are using applets, the above is not production server, it is low end
production like client machine as clients are expected to have low end systems.
> PDFBox 2.0.0-RC2 and earlie
tems.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
.
I'm really interested in the W7 performance indices. If the machine is the
future production machine, it makes sense for the manufacturer to make it
cheap. E.g. the W7 starter edition / 32 bit windows, cheap RAM, simple
mainboard, etc. As long as display and printing works properly, it doe
lman):
I remembered that I still have a laptop that is 10 years old, celeron 1.99 Ghz
CPU, 2GB RAM, 234 fonts, XP.
PDFToImage took 9 seconds the first time. After starting it repeatably, time
went down to 4 seconds. (probably parts of the JRE being cached in memory)
> PDFBox 2.0.0-RC2 and earlie
low number of fonts?
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
tal index is because I
have a low performance on aero graphics (because I have very basic graphics,
I'm not a gamer).
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB an
lman):
I remembered that I still have a laptop that is 10 years old, celeron 1.99 Ghz
CPU, 2GB RAM.
PDFToImage took 9 seconds the first time. After starting it repeatably, time
went down to 4 seconds. (probably parts of the JRE being cached in memory)
> PDFBox 2.0.0-RC2 and earlier 2.0.0 S
ve a laptop that is 10 years old, celeron 1.99 Ghz
CPU, 2GB RAM.
PDFToImage took 9 seconds the first time. After starting it repeatably, time
went down to 4 seconds. (probably parts of the JRE being cached in memory)
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
>
t a gamer).
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and low
2 GB machine with 512m and 1g option for -Xmx but no gain in
performance, results below
java –Xmx512m -jar pdfbox-2.0.0-RC2.jar PDFToImage -imageType Jpg "FontTest.PDF"
Time taken for Xmx512m: 21.66,19.89,20.11
Time taken for Xmx1g: 20.26,19.77,20.17
Don't know, since there was n
fter a fresh start, no
applications loaded, nothing else running).
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
came it took 45 sec and
subsequent time it was 18 to 19 secs. Machine has 2GB RAM.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
at more RAM results in faster rendering, up to 4GB, which makes
perfect sense.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems h
he number of fonts makes a difference. The
only number given in the previous test results is "90 fonts". Those results
seem to show that more RAM results in faster rendering, up to 4GB, which makes
perfect sense.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print perfo
nd a time window where the PC can be powered off.
I already tested low -Xmx values (50m) some days ago (when we exchanged mails)
and it worked fine. I just retested with PDFToImage and no resolution parameter
and it took about 5 seconds, maybe 6 with low memory. PC is 6 years old.
> PDFBox 2.0.0-
the font cache rebuilding message (which
should come only once).
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
not subsequent runs of PDFToImage.
Might be the font caching rebuilding message, will get you the same. Hope
deleting the .cache file and re runing might result in warning message again.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low
. Might be the font caching rebuilding message, will get you the
same. Hope deleting the .cache file and re runing might result in warning
message again. )
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower
not subsequent runs of PDFToImage.
Might be the font caching rebuilding message, will get you the same. Hope
deleting the .cache file and re runing might result in warning message again.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low
should.
I am unable to test with lower RAM and large number of fonts, hence
requested Tilman, whose machine has 492+ fonts and 8 GB RAM to reduce RAM
to 2 GB and test.
Regards
Sridhar Sowmiyanarayanan
Tata Consultancy Services
Mailto: sridhar...@tcs.com
Website: http://www.tcs.com
> PDFBox 2.0.
1 PM:
--
Thanks. I've removed the sample pdf as it was automatically attached to this
JIRA
was (Author: lehmi):
I've removed the sample pdf as it was automatically attached to this JIRA
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
&g
le pdf as it was automatically attached to this JIRA
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and low
[
https://issues.apache.org/jira/browse/PDFBOX-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler updated PDFBOX-3133:
---
Attachment: (was: FontTest.pdf)
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPS
in a machine with 2 GB RAM and 90 fonts took 17
to 18 seconds ( some warnings on fonts ){quote}
what are the warnings (that don't come in the other tests)?
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and low
ilman, whose machine has 492+ fonts and 8 GB RAM to reduce RAM
to 2 GB and test.
Regards
Sridhar Sowmiyanarayanan
Tata Consultancy Services
Mailto: sridhar...@tcs.com
Website: http://www.tcs.com
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with sys
hine with a small amount of RAM and lots of fonts? I'd
expect that the number of fonts doesn't make a difference as long as the cache
is already up to date.
There is one information missing. What kind of pdf do you use for your tests?
Can you provide us with a sample?
> PDFBox 2.0.
d be able reproduce slow performance in PDFToImage or print to see the
difference.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
e what happens (make sure
that the memory is accepted by the computer).
Desperate situations require desperate measures.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB an
27;t do anything.. If PDFToImage is slow then it's a
PDFBox issue which we can fix.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions p
You should run PDFToImage and see how long it takes to generate a PNG file,
that way we eliminate print drivers from the equation. The speed of PDFToImage
represents the speed of PDFBox, if you get slower printing performance then
it's due to Java.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SN
evel of slowness encountered).
You should run PDFToImage and see how long it takes to generate a PNG file,
that way we eliminate print drivers from the equation. The speed of PDFToImage
represents the speed of PDFBox, if you get slower printing performance then
it's due to Java. If PDFToIma
ile,
that way we eliminate print drivers from the equation. The speed of PDFToImage
represents the speed of PDFBox, if you get slower printing performance then
it's due to Java.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
rmance then
it's due to Java.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having
able. Still same issue.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
Same performance problem. CPU
consumption is only 2 to 3%. It is memory demand which is causing the delay.
Was running only Eclipse . Out of 3 GB 1.6 GB was consumed by other apps and
another 1.4 GB is available. Still same issue.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Version
d/or printer cables.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3
ents :-)
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB and lower nu
300 dpi ctors, the
printout is slow.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with systems having low RAM < 3GB an
erWidth = 3.14;
paperHeight = 50;
}
else if {
//
}
paper.setSize(paperWidth * 72.0, paperHeight * 72.0);
paper.setImageableArea(0, 0, paper.getWidth(), paper.getHeight());
pageFormat.setPaper(paper);
return pageFormat;
n use to address that as seen in PDFBOX-3046, I suspect this
issue is a duplicate of that one. Try out the solution posted there and let me
know if it works for you.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions print performance is
> poor with syst
[
https://issues.apache.org/jira/browse/PDFBOX-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson reassigned PDFBOX-3133:
---
Assignee: John Hewson
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions pr
s that as seen in PDFBOX-3046, I suspect this
issue is a duplicate of that one. Try out the solution posted there and let me
know if it works for you.
> PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions p
Sridhar created PDFBOX-3133:
---
Summary: PDFBox 2.0.0-RC2 and earlier 2.0.0 SNAPSHOT Versions
print performance is poor with systems having low RAM < 3GB and lower number of
fonts.
Key: PDFBOX-3133
URL: ht
The Apache PDFBox community is pleased to announce the release of
Apache PDFBox version 2.0.0 RC2. The release is available for download at:
http://pdfbox.apache.org/download.cgi
The numerous feedback on our first release candidate helps us to fix a lot
of issues. We'd like to
Hi,
Am 18.11.2015 um 19:46 schrieb Andreas Lehmkuehler:
Please vote on releasing this package as Apache PDFBox 2.0.0-RC2.
+1 Rey Malahay (non-binding vote)
+1 Timo Boehme
+1 Maruan Sahyoun
+1 John Hewson
+1 Tilman Hausherr
Thanks for your help and
pplication.
Tilman
Am 18.11.2015 um 19:46 schrieb Andreas Lehmkuehler:
Hi,
a candidate for the PDFBox 2.0.0-RC2 release is available at:
https://dist.apache.org/repos/dist/dev/pdfbox/2.0.0-RC2/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/p
+1 Awesome.
— John
> On 18 Nov 2015, at 10:46, Andreas Lehmkuehler wrote:
>
> Hi,
>
> a candidate for the PDFBox 2.0.0-RC2 release is available at:
>
>https://dist.apache.org/repos/dist/dev/pdfbox/2.0.0-RC2/
>
> The release candidate is a zip archive of t
+1 - thanks for preparing the RC2.
BR
Maruan
> Am 18.11.2015 um 19:46 schrieb Andreas Lehmkuehler :
>
> Hi,
>
> a candidate for the PDFBox 2.0.0-RC2 release is available at:
>
>https://dist.apache.org/repos/dist/dev/pdfbox/2.0.0-RC2/
>
> The release candid
Am 19.11.2015 um 18:02 schrieb Tilman Hausherr:
Why is
[PDFBOX-3107] Asterisk character not displaying properly in Adobe Reader
included in the release notes? This is a new, unsolved bug.
Hmm, I've used JIRA to compile the list and until now I thought that it contains
only resolved/closed tic
Why is
[PDFBOX-3107] Asterisk character not displaying properly in Adobe Reader
included in the release notes? This is a new, unsolved bug.
Tilman
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional c
Hi,
+1
checked the app-jar. My collection of problematic/error PDF now mostly
render fine.
Thanks,
Timo
Am 18.11.2015 um 19:46 schrieb Andreas Lehmkuehler:
Hi,
a candidate for the PDFBox 2.0.0-RC2 release is available at:
https://dist.apache.org/repos/dist/dev/pdfbox/2.0.0-RC2
+1
On 18 November 2015 at 11:46, Andreas Lehmkuehler wrote:
> Hi,
>
> a candidate for the PDFBox 2.0.0-RC2 release is available at:
>
> https://dist.apache.org/repos/dist/dev/pdfbox/2.0.0-RC2/
>
> The release candidate is a zip archive of the sources in:
>
>
Hi,
a candidate for the PDFBox 2.0.0-RC2 release is available at:
https://dist.apache.org/repos/dist/dev/pdfbox/2.0.0-RC2/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/pdfbox/tags/2.0.0-RC2/
The SHA1 checksum of the archive is
Am 18.11.2015 um 17:59 schrieb Tilman Hausherr:
Am 18.11.2015 um 11:44 schrieb Andreas Lehmkühler:
Tilman Hausherr hat am 18. November 2015 um 07:50
geschrieben:
Am 18.11.2015 um 07:38 schrieb Maruan Sahyoun:
I'd like to see PDFBOX-3082 to be addressed or at least the patch provided
by Tom C
Am 18.11.2015 um 11:44 schrieb Andreas Lehmkühler:
Tilman Hausherr hat am 18. November 2015 um 07:50
geschrieben:
Am 18.11.2015 um 07:38 schrieb Maruan Sahyoun:
I'd like to see PDFBOX-3082 to be addressed or at least the patch provided
by Tom Callahan to be reviewed.
It has a very high impact
> Tilman Hausherr hat am 18. November 2015 um 07:50
> geschrieben:
>
>
> Am 18.11.2015 um 07:38 schrieb Maruan Sahyoun:
> > I'd like to see PDFBOX-3082 to be addressed or at least the patch provided
> > by Tom Callahan to be reviewed.
> > It has a very high impact on memory usage and there were
Am 18.11.2015 um 07:38 schrieb Maruan Sahyoun:
I'd like to see PDFBOX-3082 to be addressed or at least the patch provided by
Tom Callahan to be reviewed.
It has a very high impact on memory usage and there were several complaints.
I hope to be able to test, review and commit the rest of his pa
Hi,
> Am 17.11.2015 um 12:54 schrieb Andreas Lehmkühler :
>
> Hi,
>
>> Andreas Lehmkuehler hat am 9. November 2015 um 18:36
>> geschrieben:
>>
>>
>> Hi,
>>
>> Am 07.11.2015 um 14:38 schrieb Andreas Lehmkuehler:
>>> On 11/06/2015 10:24 PM, Andreas Lehmkuehler wrote:
I've found work aroun
Hi,
> Andreas Lehmkuehler hat am 9. November 2015 um 18:36
> geschrieben:
>
>
> Hi,
>
> Am 07.11.2015 um 14:38 schrieb Andreas Lehmkuehler:
> > On 11/06/2015 10:24 PM, Andreas Lehmkuehler wrote:
> >> I've found work around for my problem (gfx card). It's not perfect, but it
> >> works.
> > The
Hi,
Am 07.11.2015 um 14:38 schrieb Andreas Lehmkuehler:
On 11/06/2015 10:24 PM, Andreas Lehmkuehler wrote:
I've found work around for my problem (gfx card). It's not perfect, but it
works.
The work around doesn't work for my signing environment. :-(
We have to postpone the RC
Everything work
On 11/06/2015 10:24 PM, Andreas Lehmkuehler wrote:
I've found work around for my problem (gfx card). It's not perfect, but it
works.
The work around doesn't work for my signing environment. :-(
We have to postpone the RC
BR
ANdreas
I'll try to find some time tomorrow to cut the RC .
B
I've found work around for my problem (gfx card). It's not perfect, but it
works.
I'll try to find some time tomorrow to cut the RC .
BR
Andreas
On 11/06/2015 07:58 PM, Andreas Lehmkühler wrote:
Hi,
I have bad news. After a software update my machine is somehow broken and I
couldn't get
Hi,
I have bad news. After a software update my machine is somehow broken and I
couldn't get it to run.
I'm afraid we have to postpone the RC2.
Sorry, my fault :-((
BR
Andreas
> John Hewson hat am 6. November 2015 um 19:12 geschrieben:
>
>
> Ok, I’m done making changes. PDFBOX-2950 is work
Am 06.11.2015 um 19:12 schrieb John Hewson:
Ok, I’m done making changes. PDFBOX-2950 is working well enough now. So I’m
happy for RC2.
test is running...
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For add
Ok, I’m done making changes. PDFBOX-2950 is working well enough now. So I’m
happy for RC2.
— John
> On 6 Nov 2015, at 09:21, John Hewson wrote:
>
> Hello,
>
> I’m online now and will take a look at the build issue. Sorry, I’d assumed
> that Id fixed it yesterday one my local build passed, b
> On 6 Nov 2015, at 09:30, Tilman Hausherr wrote:
>
> Am 06.11.2015 um 18:21 schrieb John Hewson:
>> Hello,
>>
>> I’m online now and will take a look at the build issue. Sorry, I’d assumed
>> that Id fixed it yesterday one my local build passed, but I don’t run
>> Isartor so I missed that one
Am 06.11.2015 um 18:21 schrieb John Hewson:
Hello,
I’m online now and will take a look at the build issue. Sorry, I’d assumed that
Id fixed it yesterday one my local build passed, but I don’t run Isartor so I
missed that one.
You probably mean Bavaria, which is disabled by default, but enabl
Hello,
I’m online now and will take a look at the build issue. Sorry, I’d assumed that
Id fixed it yesterday one my local build passed, but I don’t run Isartor so I
missed that one.
— John
> On 5 Nov 2015, at 22:30, Andreas Lehmkuehler wrote:
>
> Hi,
>
>
> Am 02.11.2015 um 12:29 schrieb An
> Am 06.11.2015 um 10:20 schrieb Andreas Lehmkühler :
>
>> Tilman Hausherr hat am 6. November 2015 um 09:36
>> geschrieben:
>>
>>
>> Am 06.11.2015 um 08:21 schrieb Maruan Sahyoun:
Am 06.11.2015 um 07:30 schrieb Andreas Lehmkuehler :
Hi,
Am 02.11.2015 um 12:29 s
> Tilman Hausherr hat am 6. November 2015 um 09:36
> geschrieben:
>
>
> Am 06.11.2015 um 08:21 schrieb Maruan Sahyoun:
> >> Am 06.11.2015 um 07:30 schrieb Andreas Lehmkuehler :
> >>
> >> Hi,
> >>
> >>
> >> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
> >>> Hi,
> >>>
> >>> do we need anothe
Am 06.11.2015 um 08:21 schrieb Maruan Sahyoun:
Am 06.11.2015 um 07:30 schrieb Andreas Lehmkuehler :
Hi,
Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
Hi,
do we need another release candidate before releasing the final version?
I would have some cycles to cut a RC2 this week only (on We
> Am 06.11.2015 um 07:30 schrieb Andreas Lehmkuehler :
>
> Hi,
>
>
> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
>> Hi,
>>
>> do we need another release candidate before releasing the final version?
>>
>> I would have some cycles to cut a RC2 this week only (on Wednesday?).
>>
>> WDYT
Hi,
Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
Hi,
do we need another release candidate before releasing the final version?
I would have some cycles to cut a RC2 this week only (on Wednesday?).
WDYT?
I'm going to cut the RC today in the evening (CET) aprox. 10-12 hours from now
BU
> On 4 Nov 2015, at 13:57, Andreas Lehmkuehler wrote:
>
> Hi,
>
> Am 02.11.2015 um 19:27 schrieb John Hewson:
>>
>>> On 2 Nov 2015, at 08:32, Maruan Sahyoun wrote:
>>>
>>> Hi,
>>>
Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler :
Hi,
do we need another release c
Hi,
Am 02.11.2015 um 19:27 schrieb John Hewson:
On 2 Nov 2015, at 08:32, Maruan Sahyoun wrote:
Hi,
Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler :
Hi,
do we need another release candidate before releasing the final version?
I'd think another RC would be good but that should potent
> On 2 Nov 2015, at 08:32, Maruan Sahyoun wrote:
>
> Hi,
>
>> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler :
>>
>> Hi,
>>
>> do we need another release candidate before releasing the final version?
>>
>
> I'd think another RC would be good but that should potentially include an
> enha
> Am 02.11.2015 um 18:36 schrieb Tilman Hausherr :
>
> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
>> Hi,
>>
>> do we need another release candidate before releasing the final version?
>>
>> I would have some cycles to cut a RC2 this week only (on Wednesday?).
>>
>
> Yes!
>
> Suggesti
Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
Hi,
do we need another release candidate before releasing the final version?
I would have some cycles to cut a RC2 this week only (on Wednesday?).
Yes!
Suggestion for announce text (additional to the usual things):
- thanks for the feedbac
Hi,
> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler :
>
> Hi,
>
> do we need another release candidate before releasing the final version?
>
I'd think another RC would be good but that should potentially include an
enhanced font cache.
BR
Maruan
> I would have some cycles to cut a RC2 t
Hi,
do we need another release candidate before releasing the final version?
I would have some cycles to cut a RC2 this week only (on Wednesday?).
WDYT?
BR
Andreas
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
Fo
97 matches
Mail list logo
