mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 01:36:03 +03:00
[GH-ISSUE #564] MD013: Unicode character width #451
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#451
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @m15a on GitHub (Aug 19, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/564
Writing texts using non-ASCII characters in markdown would be daily practice worldwide. One, like me, would want to lint markdown files written in non-ASCII characters.
Regarding MD013, the current implementation of markdownlint seems checking character count of each line, based on regular expression. However, character width of unicode characters varies. For example, CJK characters often have double width.
Imagine that you configured MD013 as
and you have
example.md:It is expected that both lines 4 and 7 are warned by MD013. However,
Related: https://github.com/psf/black/issues/1197
@DavidAnson commented on GitHub (Aug 19, 2022):
In my mind, rules about line length are meant to ensure that everything fits on the screen or that line lengths are consistent when using a monospaced font. With that understanding, the current implementation of this rule seems correct: it counts the number of visible characters. Trying to base a rule like this on the underlying encoding/representation of the data does not seem generally useful.
Something that complicates things is shown in your example: some characters may render wider then the default monospace character width. However, that is a rendering behavior that will vary by font, program, and operating system - and does not seem like it could be addressed by a rule.
As such, I feel the current implementation is valid.
@m15a commented on GitHub (Aug 20, 2022):
Agree, but displayed line lengths are inconsistent when writing CJK text since majority of monospace CJK fonts are actually duospaced.
Probably I want an option, rather than changing a rule, to customize how to measure line length, based on either the number of characters or unicode width.
@DavidAnson commented on GitHub (Aug 20, 2022):
Do you know if there is a RegExp character class to identify "wide" characters?
@m15a commented on GitHub (Aug 20, 2022):
Hmm, no. I searched for and found cjk-regex, which matches CJK characters but not all CJK characters are necessarily double width (e.g., single width
アイウエオand double widthアイウエオ).@DavidAnson commented on GitHub (Aug 20, 2022):
This part of the Unicode spec seems relevant:
As do these packages:
However, I have a strict "no dependencies" rule and I don't see a clean way of referencing this data otherwise.