bugGNU troff - Bugs: bug #55616, -T ascii rendering: do not render...


bug #55616: -T ascii rendering: do not render \(oq as "accent grave"

Submitted by:  Ingo Schwarze <schwarze>
Submitted on:  Thu 31 Jan 2019 01:00:01 PM UTC  
Category:  Font - others Severity:  1 - Wish
Item Group:  None Status:  Wont Fix
Privacy:  Public Assigned to:  Ingo Schwarze <schwarze>
Open/Closed:  Closed Planned Release:  None

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Sat 23 Feb 2019 07:13:01 PM UTC, comment #1: 

No consensus could be reached that we want this.

While arguably, producing ASCII output that is compatible with Unicode would be nice to have, it is not critically important.

On the other hand, the existing ASCII output is correct and agrees with all ASCII standards since 1965.  Several developers are still using ASCII fonts that render 0x60/0x27 as symmetric opening and closing quotes.  For those, output would look worse with the chance.  Besides, when there are neither compelling technical reasons nor a clear consensus, it is better to leave established behaviour unchanged.

Ingo Schwarze <schwarze>
Project MemberIn charge of this item.
Thu 31 Jan 2019 01:00:01 PM UTC, original submission:  

If i remember correctly, some time ago, people went through error messages and manual pages and changed single-quoted strings where the opening quote was an "accent grave" to the normal ASCII U+0027 APOSTROPHE-QUOTE because rendering single quotes like `this' was considered an anachronism from the mechanical typewriter era.

However, the -T ascii output device still renders \(oq as "accent grave", also affecting macro packages that implement single quoting macros in terms of \(oq, for example mdoc(7) .Sq.

I propose the patch below to change the -T ascii (and -T latin1) rendering of \(oq from "accent grave" to APOSTROPHE-QUOTE.  No other output device is affected.

For example, this makes -Tascii-rendered manual pages look less antique, and if this is decided, i will do the same in mandoc(1).  However, i think it's also the right thing to do for non-manual-page documents.

Issue brought up by Anthony Bentley@ (OpenBSD).

Ingo Schwarze <schwarze>
Project MemberIn charge of this item.


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files
file #46143:  oq.patch added by schwarze (743B - text/x-patch)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by schwarze (Submitted the item)
  • -email is unavailable- added by schwarze

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-02-23 schwarze Severity2 - Minor => 1 - Wish
        StatusNone => Wont Fix
        Open/ClosedOpen => Closed
    2019-01-31 schwarze Attached File- => Added oq.patch, #46143
        Carbon-Copy- => Added bentley@openbsd.org

    Back to the top

    Powered by Savane 3.5