Bug#813562: Project maintainer here
Hello, On Sat, Feb 13, 2016 at 01:35:10AM +, James R Barlow wrote: > Oh, interesting. By smaller I take it mean the file size was reduced, not > resampling of images. Any chance you can send me an example input PDF? > (Dropbox > is best.) > > I did increase the JPEG quality that Ghostscript uses when transcoding JPEGs, > mostly as an added safety margin, but I can make that optional. Maybe that > affects file size more than I thought. Turns out the new version doesn't increase the file size \o/ -- Sean Whitton signature.asc Description: PGP signature
Bug#813562: Project maintainer here
I'd suggest putting ocrmypdf in a submodule with the Debian things outside. Then setup tools should pick up tags correctly rather than generating whatever "git describe" decides to call the current revision in your merged repo. On Sat, Feb 13, 2016 at 16:46 Sean Whitton wrote: > Hello, > > Thank you for your e-mail. > > On Sat, Feb 13, 2016 at 01:35:10AM +, James R Barlow wrote: > > On Fri, 12 Feb 2016 at 17:05 Sean Whitton > wrote: > > I have a non-packaging question that I'd like to take this > opportunity > > to ask you: in your changelog entry for 3.2, it's explained that the > new > > "lossless reconstruction" feature is disabled by --deskew and > > --clean-final but otherwise PDF contents are now added to but not > > modified by OCRmyPDF. I had observed that OCRmyPDF makes my PDFs > much > > smaller without making them any harder to read, presumably by > changing > > the content, and I rather liked this feature. Can I turn it back on? > > Or was --clean-final doing this and turning that on would be enough? > > Oh, interesting. By smaller I take it mean the file size was reduced, not > > resampling of images. Any chance you can send me an example input PDF? > (Dropbox > > is best.) > > Sure, I'll do that once I can make my 3.2 package build. > > > If you build the package around a wheel or tarball obtained from PyPI, > > setuptools_scm should be able to get the version out. It will fail to > determine > > the version from a Github tarball. > > I'm trying to build out of git: I have a branch with the Debian control > files and I merged your 3.2 tag into that. Do you know how I can make > setuptools_scm successfully determine the version from that? How do you > do your builds during development? > > -- > Sean Whitton >
Bug#813562: Project maintainer here
Hello, Thank you for your e-mail. On Sat, Feb 13, 2016 at 01:35:10AM +, James R Barlow wrote: > On Fri, 12 Feb 2016 at 17:05 Sean Whitton wrote: > I have a non-packaging question that I'd like to take this opportunity > to ask you: in your changelog entry for 3.2, it's explained that the new > "lossless reconstruction" feature is disabled by --deskew and > --clean-final but otherwise PDF contents are now added to but not > modified by OCRmyPDF. I had observed that OCRmyPDF makes my PDFs much > smaller without making them any harder to read, presumably by changing > the content, and I rather liked this feature. Can I turn it back on? > Or was --clean-final doing this and turning that on would be enough? > Oh, interesting. By smaller I take it mean the file size was reduced, not > resampling of images. Any chance you can send me an example input PDF? > (Dropbox > is best.) Sure, I'll do that once I can make my 3.2 package build. > If you build the package around a wheel or tarball obtained from PyPI, > setuptools_scm should be able to get the version out. It will fail to > determine > the version from a Github tarball. I'm trying to build out of git: I have a branch with the Debian control files and I merged your 3.2 tag into that. Do you know how I can make setuptools_scm successfully determine the version from that? How do you do your builds during development? -- Sean Whitton signature.asc Description: PGP signature
Bug#813562: Project maintainer here
On Fri, 12 Feb 2016 at 17:05 Sean Whitton wrote: > Hello, > > On Fri, Feb 12, 2016 at 03:23:39AM -0800, James R Barlow wrote: > > Let me know if you'd like to see any changes to help with packaging. > > Thank you for your input, and for OCRmyPDF. > > I have a non-packaging question that I'd like to take this opportunity > to ask you: in your changelog entry for 3.2, it's explained that the new > "lossless reconstruction" feature is disabled by --deskew and > --clean-final but otherwise PDF contents are now added to but not > modified by OCRmyPDF. I had observed that OCRmyPDF makes my PDFs much > smaller without making them any harder to read, presumably by changing > the content, and I rather liked this feature. Can I turn it back on? > Or was --clean-final doing this and turning that on would be enough? > > Oh, interesting. By smaller I take it mean the file size was reduced, not resampling of images. Any chance you can send me an example input PDF? (Dropbox is best.) I did increase the JPEG quality that Ghostscript uses when transcoding JPEGs, mostly as an added safety margin, but I can make that optional. Maybe that affects file size more than I thought. > > If you are packaging around 3.1.1, versions older than 3.2.1 are > > incompatible with the recently released img2pdf 0.2.0; they require > > 0.1.5, and they do not enforce this dependency on their own. > > I've got a working package for 3.1 but I'm now trying to update my > packaging for the 3.2 series before I try to find a sponsor DD to upload > to Debian. I'm figuring out how your change to use setuptools-scm can > be made to work with the Debian toolchain. > > If you build the package around a wheel or tarball obtained from PyPI, setuptools_scm should be able to get the version out. It will fail to determine the version from a Github tarball. > My current development branch adds a new dependency on cffi (libffi) to > access > > leptonica (also a tesseract dependency), and automatic fixing of page > rotation. > > Cool! > -- > Sean Whitton >
Bug#813562: Project maintainer here
Hello, On Fri, Feb 12, 2016 at 03:23:39AM -0800, James R Barlow wrote: > Let me know if you'd like to see any changes to help with packaging. Thank you for your input, and for OCRmyPDF. I have a non-packaging question that I'd like to take this opportunity to ask you: in your changelog entry for 3.2, it's explained that the new "lossless reconstruction" feature is disabled by --deskew and --clean-final but otherwise PDF contents are now added to but not modified by OCRmyPDF. I had observed that OCRmyPDF makes my PDFs much smaller without making them any harder to read, presumably by changing the content, and I rather liked this feature. Can I turn it back on? Or was --clean-final doing this and turning that on would be enough? > If you are packaging around 3.1.1, versions older than 3.2.1 are > incompatible with the recently released img2pdf 0.2.0; they require > 0.1.5, and they do not enforce this dependency on their own. I've got a working package for 3.1 but I'm now trying to update my packaging for the 3.2 series before I try to find a sponsor DD to upload to Debian. I'm figuring out how your change to use setuptools-scm can be made to work with the Debian toolchain. > My current development branch adds a new dependency on cffi (libffi) to access > leptonica (also a tesseract dependency), and automatic fixing of page > rotation. Cool! -- Sean Whitton signature.asc Description: PGP signature
Bug#813562: Project maintainer here
Let me know if you'd like to see any changes to help with packaging. If you are packaging around 3.1.1, versions older than 3.2.1 are incompatible with the recently released img2pdf 0.2.0; they require 0.1.5, and they do not enforce this dependency on their own. If you try to install any of them now, they will pull in img2pdf 0.1.5 and break. You would need to patch in img2pdf==0.1.5. My current development branch adds a new dependency on cffi (libffi) to access leptonica (also a tesseract dependency), and automatic fixing of page rotation. -JRB
