[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #8, bug #64624 (project groff): [comment #7 comment #7:] > "grotty" needs the option '-c' to render the output correctly on a > white background. Sure, if you disable color entirely, the problem in this trivial example goes away. But if you want color, but also want pic-preproc

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #7, bug #64624 (project groff): Thanks for this additional information. It showed the way to a solution. "grotty" needs the option '-c' to render the output correctly on a white background. The output "nroff -p 2> /dev/null" shows : 536f 6d65 2074 6578 742e 0a1

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #6, bug #64624 (project groff): [comment #5 comment #5:] > To eliminate possible causes of the behaviour you observed. Do you observe different behavior? If so, where? Everything we've compared so far is identical. > Why do you not catch this illegible text in a file? Be

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #5, bug #64624 (project groff): [comment #4 comment #4:] > What are your attachments trying to illustrate? To eliminate possible causes of the behaviour you observed. Why do you not catch this illegible text in a file? __

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #4, bug #64624 (project groff): [comment #3 comment #3:] > Using "naked" diff does not provide the surroundings to pinpoint the > place where the difference occurs. A bare diff does lack context but shows line numbers. But in the comment #2 case, the location of the one line

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #3, bug #64624 (project groff): I used "test-nroff" (uses "test-groff" instead of "groff" in "nroff") which does not provide the file name. Using "naked" diff does not provide the surroundings to pinpoint the place where the difference occurs. So you have an extra line wi

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #2, bug #64624 (project groff): [comment #1 comment #1:] > Try "groff -Tlatin1 -mtty-char -Z test.pic" and compare the output > with the attached file, which is my Z-file. I needed to add the "-p" option to your command line to get meaningful results. (For this test file, the t

[bug #64624] [grotty] some pic actions make following text illegible

Follow-up Comment #1, bug #64624 (project groff): Try "groff -Tlatin1 -mtty-char -Z test.pic" and compare the output with the attached file, which is my Z-file. Test "grotty ". (file #55113) ___ Additional Item Attachment: File name

[bug #64624] [grotty] some pic actions make following text illegible

URL: Summary: [grotty] some pic actions make following text illegible Group: GNU roff Submitter: barx Submitted: Tue 05 Sep 2023 07:35:32 AM CDT Category: Driver grotty