From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>
Subject: Re: 1.11.7 minor issues
Date: Mon, 19 Sep 2011 01:54:39 +0200 [thread overview]
Message-ID: <4E7684BF.7030702@bsd.lv> (raw)
In-Reply-To: <20110918233910.GK29692@iris.usta.de>
On 19/09/2011 01:39, Ingo Schwarze wrote:
> Hi,
>
> after fixing the two larger problems, systematic comparisons
> revealed two smaller issues that are new in 1.11.7:
>
>> @@ -52,8 +52,8 @@
>> -center:off
>> -center=off
>> -center-
>> - Lynx recognizes "1", "+", "on" and "true" for true values, and "0",
>> - "-", "off" and "false" for false values. Other option-values are
>> + Lynx recognizes "1", "+", "on" and "true" for true values, and "0", "-
>> + ", "off" and "false" for false values. Other option-values are
>> ignored.
>
>> @@ -109,8 +109,8 @@
>> Many folks attempt a simple-minded regular expression approach, like
>> "s/<.*?>//g", but that fails in many cases because the tags may
>> continue over line breaks, they may contain quoted angle-brackets, or
>> - HTML comment may be present. Plus, folks forget to convert
>> - entities--like "<" for example.
>> + HTML comment may be present. Plus, folks forget to convert entities--
>> + like "<" for example.
>>
>> Here's one "simple-minded" approach, that works for most files:
>
> I will think about those two tomorrow.
Ingo,
Around line 577 in roff.c is where mandoc_hyph ended up: the quotes need
to be added.
As for the second one, we should bring jmc@ in, no? I'd think that
double or triple-dashes would be broken. Unicode, for one,
http://www.cs.tut.fi/~jkorpela/dashes.html#linebreaks
stipulates that en and em dashes break the line.
Thoughts?
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-09-18 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 23:39 Ingo Schwarze
2011-09-18 23:54 ` Kristaps Dzonsons [this message]
2011-09-19 7:58 ` Ingo Schwarze
2011-09-19 8:10 ` Kristaps Dzonsons
2011-09-19 8:41 ` Ingo Schwarze
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=4E7684BF.7030702@bsd.lv \
--to=kristaps@bsd.lv \
--cc=schwarze@usta.de \
--cc=tech@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).