But the most amazing things that Rust is a language without GC and with memory safety
and it is completely new and revolutionary
Well, I must say bye, for now, it's nice to have a conversation with you, learned couple of thing amidst resolving the installation issue. Thanks a ton!
@dashish333 and @rsprabha here are some other GN resources you might find useful:
https://github.com/gnames/gntagger
@rsprabha and @dashish333 I made a draft RFC document for
gnfinder+ project: https://github.com/gnames/gnfinder/wiki/RFC-for-%22gnfinder-plus%22-project
Hi @dimus,
After reading RFC I wrote a tiny go CLI application for gnfinder+
https://github.com/harshzalavadiya/gnfinder-plus
As of now it's just a simple binary there's no gRPC or file URL support included
Cross compiled binaries are available in releases
p.s. I'm from strand biodiv team
however pdfcpu lakes plain text output so I have to use library that uses unipdf behind the scenes
@harshzalavadiya thats great! And I think it is way better to move little by little with new functionality, find and solve problems of practical use that are appearing in the process, than try to implement everything and find that the project cannot be used for one or another reason, I am looking at your code now
@rsprabha I am glad we have some practical results from our conversation!
@harshzalavadiya first quick note. I see that you released v1.0.0, from the point of semantic versioning it is a very serious statement, that means you are not going to change API of your project until the release of v2.x.x. I would suggest to start with v0.x.x and move forward until you feel that the API is well designed and is stable for a foreseable future
btw https://github.com/lu4p/cat/blob/master/LICENSE might be problematic
@dimus looked up the lu6p unlicense. Seems to be approved by the FSF and GPL compatible. https://en.wikipedia.org/wiki/Unlicense Do you see a problem with using this library?
https://github.com/lu4p/cat uses (cloned for some reason) unipdf, which in my understanding means that it also should be AGPLed, or have a AGPL-compatible license instead of https://github.com/lu4p/cat/blob/master/LICENSE
@rsprabha :arrow_up:
v1.0.0 was given just because i was just trying out for fun and wanted to trigger CI build, as of now this repo under @harshzalavadiya is completely recycable and git history will be removed if we decide to use this repo so please ignore version or commits as of now :P
I also found one more library https://github.com/sajari/docconv (MIT License) so we can avoid AGPL and this might ease it for everyone incl. for the folks who uses it for commercial usage, and also has a optional https://github.com/otiai10/gosseract support and exactly what we need, I have updated repo that uses docconv now https://github.com/harshzalavadiya/gnfinder-plus, also I have started using proper sementic releases from now on
@harshzalavadiya great news! Can you investigate if there is a difference in handling a 2-column PDFs by either
unipdf or docconv? If one of them supports 2 column layouts, and other does not, I think it is more important than AGPL license. Most tools do not support 2 columns sadly.
@harshzalavadiya looks like
docconv is a wrapper to pdf2text command line tool, which means an introduction of an external dependency that has to be installed independently of gnfinder-plus. Because of that, I would say your unipdf solution has an advantage over docconv solution.
I added info about docconv and gnfinder-plus to https://github.com/gnames/gnfinder/wiki/RFC-for-%22gnfinder-plus%22-project
@gdower, @mju looks like symposia at TDWG is very collection oriented, and the work on CoL-BHL integration does not fit. However there is a plenary section that seem to fit this work, should we write and abstract to fit this section? https://www.tdwg.org/conferences/2020/session-list/#pd01%20avenues%20into%20integration:%20communicating%20taxonomic%20intelligence%20from%20sender%20to%20recipient
My understanding it is more about what Nico Franz is doing, however I think taxonomic intelligence has a broader sense, like 'Animal', 'Bear' 'Ursus arctos', 'Ursus arctos L. 1758', 'Ursus arctos L. 1758 sensu A.B. C' all carry some taxonomic inteligence and their meaning would significantly shift depending on a context
You should get an email with a link that will let you see and edit it in the future.
