Done and launched. -----Original Message----- From: Tilman Hausherr [mailto:[email protected]] Sent: Wednesday, July 08, 2015 3:00 AM To: [email protected] Subject: Re: PDFBox 1.8.10 release
Am 08.07.2015 um 04:20 schrieb Allison, Timothy B.: > Had to dig into code to make sure that our extension of PDFTextStripper winds > up calling the code that you are interested in. I think it does, so, yes, > all we'd have to do is two builds, one with and one without the change. > > Should I make the change locally or do you plan to commit? Locally would be best, as it is really just 1 line, and I haven't created an issue yet. Tilman > > Thank you! > > -----Original Message----- > From: Tilman Hausherr [mailto:[email protected]] > Sent: Tuesday, July 07, 2015 3:59 PM > To: [email protected] > Subject: Re: PDFBox 1.8.10 release > > Am 07.07.2015 um 19:16 schrieb Allison, Timothy B.: >> Will create separate wrapper that relies solely on PDFTextStripper instead >> of what we currently do now. Results in a few days... > This sounds like work. Isn't all that is needed to run a version before > the change, one after the change, and display the differences as a table > like you already do? > > Tilman > >> Thank you, Tilman, for pinging me. :) >> >> -----Original Message----- >> From: Andreas Lehmkühler [mailto:[email protected]] >> Sent: Thursday, July 02, 2015 2:24 AM >> To: [email protected] >> Subject: Re: PDFBox 1.8.10 release >> >> Hi, >> >>> Tilman Hausherr <[email protected]> hat am 1. Juli 2015 um 21:22 >>> geschrieben: >>> >>> >>> Am 30.06.2015 um 12:20 schrieb Andreas Lehmkühler: >>>> Hi, >>>> >>>> there are again a number of solved issues and I'm thinking about a new >>>> bugfix release. How about a new one next week, maybe later if someone >>>> wants to get some addtional things done before? >>> I have only one thing I'd like to test, with Tim Allison, before a >>> release: there's a line in PDTextStripper >> I'm not in a hurry ... >> >>> if ((wordSpacing == 0) || (wordSpacing == Float.NaN)) >>> >>> however wordSpacing == Float.NaN is always false. So I'd like to find >>> out if there is any difference in using what the developer probably >>> intended, which is >>> >>> if ((wordSpacing == 0) || (|Float.isNaN(|wordSpacing))) >>> >>> (BCC to Tim) >>> >>> Tilman >> BR >> Andreas >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
