Repository navigation
docs(site): explain dictionary input checks with executable UTF-8 examples - #3906
Merged
Merged
Conversation
…mples Publish one dated bilingual source-configuration tutorial with an executable read-only example and explicit test limits. Signed-off-by: LauraGPT <zhifu.gzf@alibaba-inc.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Publish one Shanghai 2026-11-16 bilingual tutorial about diagnosing CharTokenizer segmentation-dictionary input. The executable UTF-8 inspector reports blank lines, duplicate keys with line numbers, empty mappings, BOM characters and uppercase keys without modifying the file.
The article distinguishes main's #3905 correction from the already published 1.4.26 wheel, and distinguishes file-format checks and synthetic CUDA input-chain evidence from pretrained ASR quality. It does not reinterpret model licensing or claim adoption, performance or benchmark improvements.
Scope
Five files: two existing-template article pages, the blog catalogue, legacy manifest and focused regression tests. Existing architecture and selected/lead entries remain unchanged. No runtime, model, dependency, workflow, service, production configuration or logging change.
Validation
Inline self-reviewed with Codex assistance; no independent GitHub review is claimed. Signed and DCO-signed-off. Nano remains paused, and the pre-existing package releases are not republished by this change.