is very often used to create wrappers around other libs. This is a testament to its excellent syntax and development environment that this is deemed worthwhile. But it also produces the curious effect that I've experienced many times: you inquire of the library steward, "How does this work?" or "how can I do XYZ?" and they respond, "I'm not sure..."

@worldsendless I'm not sure if I understand this post. Anyway, I usually avoid using a wrapper, except very famous one like next.jdbc. My program usually calls Java lib directly.
Follow

@veer66 I have seen this on clj-pdf, which wraps something or other pdf, and on Juxt Tick, both very useful libraries but sometimes with the same strange characteristic that their owners don't seem to fully understand how their own system works, so answers include more "should work" and "maybe"s than expected.

@worldsendless I decided to use pdfbox directly. I had so many sad histories with wrapper since 2011 (in JS).

@veer66 oh--is that what cljpdf is wrapping? A big java lib, I guess?

@worldsendless Yes, I guess so. I saw openpdf as a dependency in their project.clj.

@worldsendless I created a wrapper too. I forgot this. :agummyoh:

And, what you mention is right. I have only a little knowledge about PDFBox.

https://github.com/veer66/pdf-to-text/blob/master/src/pdf_to_text.clj

@veer66 ooh. I sometimes use regular pdftotext heavily, and it has some big issues with multi-column pdfs. How does your apache version stack up?

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.