matthewwithanm / matthewwithanm/python-markdownify
Inconsistent handling of No-Break Space and Space
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 203
- PR merge metrics
- No merged PRs in 30d
Description
I noticed an inconsistent handling of No-Break Space and Space.
Observed behaviour using version 0.14.1: the following HTML:
<div>this is a <i>test </i>with whitespaces</div>
<div>this is a <i>test </i>with whitespaces</div>
Gets converted to:
this is a *test*with whitespaces
this is a *test* with whitespaces
Note that the in the first line gets lost during conversion.
I would expect that the conversion holds the same result for both lines. In fact I would expect the following result:
this is a *test *with whitespaces
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the two HTML examples from the issue against version 0.14.1, then trace how No-Break Space and regular Space are handled during conversion around emphasis. Done means both inputs preserve equivalent spacing and produce the expected Markdown output shown in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100