Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

SCRIP-METRIC-003: ship local UTF-8 analysis as private JSON and offline HTML

未关闭
#269 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@andy-zen-dev 已经在做这个了。

开始于 2026年10月7日。

  • #270 来自 @andy-zen-dev —— 未关闭
  • #276 来自 @andy-zen-dev —— 未关闭

评估

这个 Issue 还没有评估数据。

描述

Outcome / priority

Implement the P3 local-text delivery task already recorded in #268's compact queue. A reader or writer can analyze a local UTF-8 file with one command and get deterministic JSON or a readable offline report. This is independent of corpus/source-match blockers and #268.

Scope / claim

Claimed by andy-zen-dev at master abe7bb889ef98437ba9faef5a79b023499556991: scriptorium/analyze.py, focused tests, docs/LOCAL_ANALYSIS.md, an additive README example and a changelog delta. Revalidate/adopt the pending local-analysis work; do not duplicate or change the existing metric engine.

Acceptance

  • Use analyze_deterministic_metrics directly; retain all 29 current rows, units, profile versions, dependency identity, raw/normalized hashes and explicit short-input limitations.
  • UTF-8 input; optional dictionary and profile supplied together. Missing/undefined values are not zero or parity passes. Dictionary content and manuscript prose must not be embedded or transmitted.
  • Deterministic escaped standalone HTML, readable tables and keyboard access; no remote assets or analytics.
  • Create-only output; preserve inputs/existing outputs, including aliases and symlinks; useful errors on invalid UTF-8 and file failures.
  • Positive/negative tests, CLI smoke with the actual engine in hosted full-suite CI, and deterministic rebuilds.

No analyzer formulas, scientific completion, corpus admission, morphology substitution, Pages activation or registry publication. Later exact-head acceptance is required before merge.

主要语言
Python
星标
4
派生
0
平均合并
10 小时 58 分钟
30 天内合并 PR
78

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

drevendev/Scriptorium 的其他 Issue

查看 drevendev/Scriptorium 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。