Add Mixed Encoding Detection and Conversion Support - Resolves #25 #91
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.
Pull Request Description
Overview
This PR adds mixed encoding support to
enca, resolving issue #25 where files with multiple encodings (e.g., GB2312 + UTF-8) could not be processed.Features
Detects multiple encodings within one file, reports segments with offsets and lengths.
Default 1024 bytes, range 1–1048576. Smaller = finer detection, larger = faster.
Skips corrupted/unknown segments, falls back to predominant encoding.
Converts each segment individually while preserving file integrity.
Usage
Implementation
Documentation
Updated man page and CLI help with examples
Resolves issue can't convert mixed encode file #25: mixed encoding files could not be converted