Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Adopt the deferred private EPUB ingestion prototype into the canonical Reader

Chiusa
  • Qualcosa non va?
#289 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
24/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, cli, security, testing

Direzione di ricerca

Start by locating and inspecting any surviving EPUB handoff, then compare it with the canonical ingestion layer and current analyzer. Define the supported EPUB subset, reading order, identities, and archive safety limits before integrating useful code. Run the installed CLI through HTML, JSON, and CSV tests using small synthetic fixtures; done means the listed acceptance checks pass and the input subset and failures are documented.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Recovered product debt

Current README and the historical #274 delivery record explicitly retain unpublished EPUB/batch Workbench work. It was not part of the accepted UTF-8 Reader integration (#273/#276), nor of #288's report comparator. Open/closed issue and PR searches found no delivered EPUB integration. The prototype bytes were not recovered in this session; the historical claim is not implementation or test evidence.

User outcome

Analyze a locally supplied, unencrypted EPUB with the same canonical metrics, without uploading the book, executing embedded content or silently treating a container file as its literary body.

Acceptance

  • First locate and inspect any surviving handoff; deduplicate against current source. Recover only useful code into the canonical ingestion layer, not a parallel Workbench/analyzer.
  • Explicit supported EPUB subset and reading-order policy; separate raw archive, extracted body and normalized-text identities and versions. Preserve editions/translations as distinct inputs.
  • Bounded archive/member counts, compressed and expanded bytes; reject traversal, duplicate/ambiguous members, encrypted input, unsupported structures and unsafe XML. Never execute scripts, follow remote resources, write archive paths or bypass DRM.
  • Reuse the actual analyzer and current privacy/error/create-only output semantics; short-text representativeness remains explicit.
  • Real installed CLI -> HTML/JSON/CSV tests with small original synthetic fixtures: reading order, Unicode, missing spine, malformed archives and size/path attacks. No full copyrighted books in fixtures or reports.
  • Document the accepted input subset and failures. No corpus admission, FantLab-input match, new backend or parity claim. M2 remains 0/5.

Independent of #280 browser report comparison. Keep execution ordering in the existing compact project queue; do not create a competing worker or speculative integration branch.

Lingua principale
Python
Stelle
4
Fork
0
Merge medio
1g 8h
PR unite (30g)
36

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di drevendev/Scriptorium

Tutte le issue di drevendev/Scriptorium

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.