discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Pali Rohar <pali.rohar@gmail.com>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Undesirable space after parenthesis in HTML output
Date: Thu, 22 Nov 2018 15:08:07 +0100	[thread overview]
Message-ID: <20181122140807.GF35604@athene.usta.de> (raw)
In-Reply-To: <20181105200300.rnllxci2uhfj5w47@pali>

Hi Pali,

Pali Rohar wrote on Mon, Nov 05, 2018 at 09:03:00PM +0100:

> For following sequence in manpage
> 
>   Name (\fItest@example.org\fR)
> 
> mandoc's HTML output prints following:
> 
>   Name ( <i>test@example.org</i>)
> 
> It adds additional space after left parenthesis, which looks really
> horrible.

With -current mandoc code, i can't seem to reproduce your issue:

$ echo 'Name (\\fItest@example.org\\fR)' | mandoc -T html | grep Name
<div class="manual-text">Name (<i>test@example.org</i>)</div>

Which version of mandoc are you using?  Please state:
 - operating system name and version
 - whether contained in the base system, installed from a package,
   or compiled from source
 - if from a package, package manager name (e.g. pkgsrc, homebrew, dpkg)
   and package name and version number
 - if from source, tarball name or CVS checkout date and time

> In utf8, ps and pdf outputs it is correct without additional space:
> 
>   Name (test@example.org)

Yes, that is how it is supposed to look like.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

  reply	other threads:[~2018-11-22 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 20:03 Pali Rohár
2018-11-22 14:08 ` Ingo Schwarze [this message]
2018-11-22 14:24   ` Pali Rohár
2018-11-23 19:30     ` Ingo Schwarze
2018-11-23 20:22       ` Pali Rohár

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181122140807.GF35604@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mandoc.bsd.lv \
    --cc=pali.rohar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).