As stated in issue #96 , Japanese should be regarded as a "no space language",
and separate treatment from Chinese language is unnecessary.
Description
Concatenated japaneseRange var into noSpaceRange and removed test for !japaneseChars.test(d).
Fortunately, since Japanese shares separation characters with Chinese,
there was apparently no need to augment splitChars.
Also added a minimal test following Chinese, Lao, Burmese examples.
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
[ ] I have documented all new methods.
[ ] I have written tests for all new methods/functionality.
[ ] I have written examples for all new methods/functionality.
As stated in issue #96 , Japanese should be regarded as a "no space language", and separate treatment from Chinese language is unnecessary.
Description
Concatenated
japaneseRange
var intonoSpaceRange
and removed test for!japaneseChars.test(d)
. Fortunately, since Japanese shares separation characters with Chinese, there was apparently no need to augmentsplitChars
.Also added a minimal test following Chinese, Lao, Burmese examples.
Types of changes
Checklist