[bug #62494] [grotty] Remap ~ and ^ to their ASCII equivalents

Follow-up Comment #3, bug #62494 (project groff): I had almost given up hope, but maybe we can still get these particular changes for these five input glyphs reverted? It looks like they are more controversial than people thought, and John's suspicion that the number of complaints will only grow

[bug #62494] [grotty] Remap ~ and ^ to their ASCII equivalents

Follow-up Comment #2, bug #62494 (project groff): [comment #1 comment #1:] > It also puts additional stress on manual page writers, who are often programmers with no particular interest in typesetting That argument also goes both ways: programmers with an interest in typesetting should know

[bug #62494] [grotty] Remap ~ and ^ to their ASCII equivalents

Additional Item Attachment, bug #62494 (project groff): File name: glyph-comparison.png Size:20 KB ___ Reply to this item at:

[bug #62494] [grotty] Remap ~ and ^ to their ASCII equivalents

Follow-up Comment #1, bug #62494 (project groff): Indeed. I said before, and will say again in this context, that i would prefer keeping these mappings in manual pages (i won't type any punctuation characters here for fear that the weird Savannah web interface might mangle stuff): input ->

[bug #62494] [grotty] Remap ~ and ^ to their ASCII equivalents

URL: Summary: [grotty] Remap ~ and ^ to their ASCII equivalents Project: GNU troff Submitted by: alhadis Submitted on: Sat 21 May 2022 03:34:14 AM AEST Category: Device -

[bug #62042] [man]: want designed, documented CHECKSTYLE feature

Follow-up Comment #12, bug #62042 (project groff): Thanks for following up, Alex. It was my fault. I misspelled the name of the leading space(s) macro I offered you in comment #8. Also, in case you _don't_ want to throw away the output with `-z`, it is helpful to append to the existing

[bug #62042] [man]: want designed, documented CHECKSTYLE feature

Follow-up Comment #11, bug #62042 (project groff): Hi Branden, [comment #10 comment #10:] > I am confused. This appears to be working exactly as I intended. Did I misunderstand what you wanted? Yup, check ; it's supposed to cancel the effects of for leading spaces and blank lines, isn't it?

[bug #62357] [build] tests using "locale charmap" skipped on macOS

Follow-up Comment #17, bug #62357 (project groff): Good deal! Thanks, John. ___ Reply to this item at: ___ Message sent via Savannah

[bug #62357] [build] tests using "locale charmap" skipped on macOS

Follow-up Comment #16, bug #62357 (project groff): [comment #15 comment #15:] > Please try the attached patch and let me know if the test passes after applying it. That seemed to do the trick! I've attached the build log. (BTW, I remembered I still had a /usr/local/share/groff from a previous

[bug #62357] [build] tests using "locale charmap" skipped on macOS

Follow-up Comment #15, bug #62357 (project groff): Hi John, Please try the attached patch and let me know if the test passes after applying it. Since I'm still puzzled about the "SKIP" results, you might need to try it after cleaning the tree. "make -j check" should do the build _and_ the

[bug #62357] [build] tests using "locale charmap" skipped on macOS

Follow-up Comment #14, bug #62357 (project groff): [comment #11 comment #11:] > The problem is a divergence between Linux 'od -c' output and macOS (BSD?) 'od -c' output. Except I haven't heard any complaints from Ingo, so this may be a true macOS-ism. This might make your life easier: