Add support for character encoding configuration (Fixes #46) #1
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
Problem Solved
Resolves issue #46 where special characters are not handled correctly due to encoding mismatches between Java and Node.js components.
Changes Made
Core Implementation
javaEncodingparameter to constructor options-Dfile.encodingJVM parameter whenjavaEncodingis specifiedTesting & Documentation
New API Usage
Common Use Cases
encoding: 'latin1', javaEncoding: 'Cp1252'encoding: 'latin1', javaEncoding: 'ISO-8859-1'Backward Compatibility
✅ All existing code continues to work without changes
✅ New parameters are optional
✅ Java constructors use method overloading (no breaking changes)
✅ Default behavior unchanged
Test Results
🤖 Generated with Claude Code