manual line splits in poetry don’t always work
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
If you use "//" to indicate where to split a line, sometimes it doesn’t work. E.g. with this text:
the first break happens, but the second one doesn’t:
Maybe something about being earlier in the line?
So I thought I would work around that by creating a change which adds in a \u2028 to manually break the line and remove the //, and it makes the manual break, but it also splits the remaining line into two sections!
My workaround was to add some more text at the beginning of the line, and then it worked for me.
Attached is the archive file which reproduces the problem.
EJF-EZR-NEHPTXprintArchive.zip
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
Start by unpacking EJF-EZR-NEHPTXprintArchive.zip and reproducing the manual // line-split failure in the USFM/XeTeX workflow. Compare the first and second breaks, including the workaround using a Unicode line separator and added leading text. Done means manual splits work consistently without dividing the remaining line into unintended sections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tex
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100