From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: *** X-Spam-Status: No, score=3.4 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED, SPOOFED_FREEMAIL autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 26594 invoked from network); 15 Oct 2020 20:48:42 -0000 Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12) by inbox.vuxu.org with ESMTPUTF8; 15 Oct 2020 20:48:42 -0000 Received: from fantadrom.bsd.lv (localhost [127.0.0.1]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 0034e2d2 for ; Thu, 15 Oct 2020 15:48:39 -0500 (EST) Received: from mail-il1-f174.google.com (mail-il1-f174.google.com [209.85.166.174]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 61a1092e for ; Thu, 15 Oct 2020 15:48:38 -0500 (EST) Received: by mail-il1-f174.google.com with SMTP id j8so6438989ilk.0 for ; Thu, 15 Oct 2020 13:48:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pbZbVKwa24ZmwyOZvGROXRrlWcOgVdWE2zEHSZmFQHk=; b=sAoJC2BtCv37e/H1o3uuSCo75FUP5XutMvV+ja8FQpnGZNJDal5ucFt1MRWlX4Iib3 9PLpAXpW2vhDjXZQOF1X3gRk+gIKbsdZDf7U2ESUXEKz+Czk91pEfcLFyRJqd4xwAF4s hVzzddi+Vpe4rtSC5LsxsXTWPXmkCf6zq/PhblIeI3fNWiQWovohlWgx233IOKGvVSxI AwjWile7XS7+5vm1UeAAybEkHj3Sin54udTHsopDNbfAIbV5NjuG2EGr94MXiVX4OQlI lO+f3b9pLWezuCy6+ZfJy+j/cnZiI7Bwwf1F2OxBAQsFbvvJT2eLJgGwnqIFqRmWdvO1 QY3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pbZbVKwa24ZmwyOZvGROXRrlWcOgVdWE2zEHSZmFQHk=; b=k1mInurOrVE8J11G/uOj0W0/sEDbT20clMbNb2ZOhLJh3obAOGzUKsNBnMEFKDYFIr Y1lyl8UeglxgHY1pQmFHnN2jwbcn68arvOAnIIJ0vvtZmNlEdyLb0y/npQCrw67A07MH 8hfm04ds+BBdd7IYBcsmUa9+mvgCpyC/Uf57L1q/3qN+eRsHhc5ZuxBDzy3gVJUjrXvf 6Oi9wusRz8tUFoE+rGnVe419CS7h94wUWr9Bkg8JzpzQrHBFMUQ1F3niFwJIXUr+vfoT 1kYaXISf8LFEq1aoW7mHH7AQetGxCh7ieRMm+AIwEiqsWFD8uiXaPrUQUcp6+N6UlTUD Zo7w== X-Gm-Message-State: AOAM5331FuM4bI12kraKf0lriq/P2NotRZh6SSMiPsC57XQTtC9yTIxg 37jn1YLYyJPzP3iV9sqj4ZhyrBUoGGlZnuT/4T8G4Fxg74w= X-Google-Smtp-Source: ABdhPJzbBQe0lJwChkSdXIYrHS15DycP0apPlGrOqTxZefGgVSSyyINkRZa7dG6G7fYAdY83K5QcxOKnKfMNPbXjE5o= X-Received: by 2002:a92:194a:: with SMTP id e10mr365552ilm.26.1602794916969; Thu, 15 Oct 2020 13:48:36 -0700 (PDT) X-Mailinglist: mandoc-discuss Reply-To: discuss@mandoc.bsd.lv MIME-Version: 1.0 From: Aman Verma Date: Thu, 15 Oct 2020 16:48:50 -0400 Message-ID: Subject: In HTML output literal blocks should strip newline before closing pre To: discuss@mandoc.bsd.lv Content-Type: text/plain; charset="UTF-8" The problem with `.Bd -literal` blocks in HTML output is that mandoc doesn't output the closing pre tag on the same line. If the element is indented, browsers will display an extra line since pre is telling them to preserve whitespace. A good example of the issue is . The extra space is clearly visible. The source is
.Nm name0 ,
    .Nm name1 ,
    .Nm name2
    .Nd a one line description
        
What I'm proposing is that it should look like
.Nm name0 ,
    .Nm name1 ,
    .Nm name2
    .Nd a one line description
This is what most Markdown processors do to solve the issue. Best regards, Aman -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv