Closed ljrk0 closed 5 years ago
Thank you for reporting, the latest commit should fix it.
However with \fCW
I didn't have any issues in the first place for some reason. Or perhaps a paragraph just moved in a way that it looked like it, I thought the issue was on my side.
Sorry, the commit message went wrong, I did use @Leonard instead of @LeonardKoenig ... Not easy to fix since commit is pushed already...
It does work for CW since no font name mapping needs to be applied for CW (it is the original name), but CR needs to be mapped to CW... This had been done at document start but not after a page break.
Not easy to fix since commit is pushed already...
It's not too late to force-push an amended commit, is it?
$ git commit --amend
…
$ git push origin master --force
Ah, that makes sense, thanks for explaining!
No problem, perhaps the other guy might wonder why they get notified, though. Rewriting something officially pushed is not so good, but it's not that late, but don't bother for me.
@Alhadis thank you, applied.
Edit: Nevermind, after hours of debugging: It was just a typo, my bad.It was a bug after all...
I've observed the behavior that if one paragraph crosses the boundary of a page, selecting the constant-width fonts is not working correctly. Here's a test file: test.pdf, it only contains the line
all over again.
To show the difference between one line on the first page and one on the second, I made to screenshots:
![second page](https://user-images.githubusercontent.com/7831843/46881687-8b9da180-ce4c-11e8-9ec8-242a227c5cd9.png)
Setting
.do xflag 3
does not change the behavior.I'm running latest git (6fa0ad8) heirloom troff on Arch using:
Thanks for this awesome work though!