Yes, I've been wondering about the best approach with that. Obviously,
better quality is better, but we don't want to overwhelm the various
tools that deal with the DjVus.
And if we're building DjVus for Commons from IA files (either PDFs or
the Jpegs), should we also be adding those DjVus back to the IA item?
(Actually, can we even edit IA items that we haven't created ourselves?)
I'm figuring not doing so (but maybe adding a comment to the IA item
that links to the DjVu on Commons).
On Mon, 2 Jan 2017, at 05:08 PM, Alex Brollo wrote:
> About djvu files on IA, they can be built simply by pdf2djvu from pdf
> files of IA, but quality is very poor; or they can be built, with some
> more pain, from _jp2.zip images merged with _djvu.xml files, the
> quality is high but resulting djvu is heavy.
> As Aubrey told some time ago, it.source uses a python script to do the
> latter job, but it is a DIY (do it yourself) script, just to proof
> that *it can be done*.
2017-01-02 5:29 GMT+01:00 Sam Wilson
> Hi all,
> I've attempted to start a phab ticket about
what the import wizard
> should look like:
> There are plenty of unanswered questions I'm
sure, and lots missing
> still. Please edit the task or add comments about anything.
> This is 2016 Wishlist #73, so I'm not sure
it'll get much 'official'
> comm-tech time (yet; there *is* a plan to address further-down
> but they may take some time), but I'm keen to work on it in my
> own time
> One thing I'd love to have in a Wikisource
upload wizard is a
> thing that
> I can show to Glam people that makes it easier for them to see
> the value
> (and ease) in getting their stuff online and ready for crowd-sourced
> transcription. :-)
> Wikisource-l mailing list
Wikisource-l mailing list