discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: .Fn _* issue
Date: Sat, 25 Sep 2010 23:29:39 +0200	[thread overview]
Message-ID: <4C9E69C3.2050009@bsd.lv> (raw)
In-Reply-To: <20100925212507.GM25298@bramka.kerhand.co.uk>

Jason McIntyre wrote:
> On Sat, Sep 25, 2010 at 10:18:07PM +0200, Kristaps Dzonsons wrote:
>>> hmm. i use TERM=wsvt25. so do you think there is a bug in the term code,
>>> or it's something else?
>> There's nothing mandoc can do about it: the "_" character produces the
>> same escape sequence when it's underlined as when it's bold ("_\b_").  I
>> observe that, in this situation, the "underline" style has precedence
>> (by colouring on the "linux" terminal).
> 
> so why groff displays "correctly" and mandoc not? the terminal
> interprets those sequences? and i should just accept that there's a bit
> screw up?
> 
> (not arguing, just clueless)

Can you produce a hexdump of the escape sequence groff uses for the 
offending phrase?  I couldn't find any difference in groff and mandoc 
output.
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-09-25 21:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  6:35 Jason McIntyre
2010-09-25 15:23 ` Kristaps Dzonsons
2010-09-25 15:35   ` Jason McIntyre
2010-09-25 15:45     ` Kristaps Dzonsons
2010-09-25 17:47       ` Jason McIntyre
2010-09-25 20:18         ` Kristaps Dzonsons
2010-09-25 21:25           ` Jason McIntyre
2010-09-25 21:29             ` Kristaps Dzonsons [this message]
2010-09-25 21:38 ` Ingo Schwarze
2010-09-25 21:43   ` Joerg Sonnenberger

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=4C9E69C3.2050009@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=discuss@mdocml.bsd.lv \
    /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).