From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.comp.tex.texinfo.bugs,gmane.emacs.devel Subject: Re: texi2html output validity Date: Tue, 23 Dec 2014 15:37:30 +0000 Message-ID: <87y4pyfkcl.fsf@violet.siamics.net> References: <87388bnzha.fsf@newcastle.ac.uk> <87k31mdbhe.fsf@uwakimon.sk.tsukuba.ac.jp> <87tx0qiv45.fsf@fencepost.gnu.org> <87h9wqd3i5.fsf@uwakimon.sk.tsukuba.ac.jp> <87h9wqimf0.fsf@fencepost.gnu.org> <87y4q1fekv.fsf@fencepost.gnu.org> <87k31kga2y.fsf@fencepost.gnu.org> <87r3vsdps7.fsf@fencepost.gnu.org> <87a92ehctk.fsf_-_@violet.siamics.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1419349074 9670 80.91.229.3 (23 Dec 2014 15:37:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Dec 2014 15:37:54 +0000 (UTC) To: bug-texinfo@gnu.org, emacs-devel@gnu.org Original-X-From: bug-texinfo-bounces+gnu-bug-texinfo2=m.gmane.org@gnu.org Tue Dec 23 16:37:50 2014 Return-path: Envelope-to: gnu-bug-texinfo2@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Y3RWv-00044J-F3 for gnu-bug-texinfo2@m.gmane.org; Tue, 23 Dec 2014 16:37:49 +0100 Original-Received: from localhost ([::1]:45201 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3RWu-0005po-JG for gnu-bug-texinfo2@m.gmane.org; Tue, 23 Dec 2014 10:37:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57255) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3RWr-0005mz-4q for bug-texinfo@gnu.org; Tue, 23 Dec 2014 10:37:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y3RWq-0006Z3-0B for bug-texinfo@gnu.org; Tue, 23 Dec 2014 10:37:45 -0500 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:52094) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3RWn-0006Y8-1X; Tue, 23 Dec 2014 10:37:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=GNxxBDEN4J13B0qUc+tmMBk5jioMghTV+CzqtNWYUxs=; b=SC84vuK+O+MTkC+rQbtp9CzXQjJGwERMI/ZkvF3GQKRq74wlYYAbUSMw9dHQIBz9LbAEEXLUPLXIT1iBm7+1+Y+iqTNtsehiVhF0pXXq7bVw0KWJ/pj9DAiqDpvF/BMFjjlNRZqXGfP1v142bJR7GYMwpHU9VRYyDHI7aOeGM1s=; Original-Received: from [2a02:2560:6d4:26ca::1:1d] (helo=violet.siamics.net) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Y3RWk-00046L-RR; Tue, 23 Dec 2014 15:37:39 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Y3RWc-0002Bo-MO; Tue, 23 Dec 2014 22:37:30 +0700 Mail-Followup-To: bug-texinfo@gnu.org, emacs-devel@gnu.org In-Reply-To: (Yuri Khan's message of "Tue, 23 Dec 2014 21:29:07 +0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:4f8:d15:1b86::2 X-BeenThere: bug-texinfo@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-texinfo-bounces+gnu-bug-texinfo2=m.gmane.org@gnu.org Original-Sender: bug-texinfo-bounces+gnu-bug-texinfo2=m.gmane.org@gnu.org Xref: news.gmane.org gmane.comp.tex.texinfo.bugs:6979 gmane.emacs.devel:180571 Archived-At: >>>>> Yuri Khan writes: >>>>> On Tue, Dec 23, 2014 at 4:37 PM, Ivan Shmakov wrot= e: >>>> In this snippet, I count 2 instances of improper tag nesting, >> I count just a single one, but yes, that second

surely >> invalidates the fragment. >

is improper* nesting in my book. All paired tags SHOULD** > be explicitly closed. > * note I did not say =E2=80=9Cinvalid=E2=80=9D Yes; but /I/ did. And the HTML5 TR agrees with me on that [1]: A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, div, dl, fieldset, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, nav, ol, p, pre, section, table, or ul, element, or if there is no more content in the parent element and the parent element is not an a element. [1] http://www.w3.org/TR/html5/syntax.html#optional-tags > ** as in RFC2119 The problem with =E2=80=9Cbooks=E2=80=9D is that every other participant t= o this discussion will have his or her own one. My own preference is to write void elements like

, and to spell out the opening and closing tags for all the other elements, =E2=80=93 /unless/ there=E2=80=99s a reason not to (say, for educational purposes.) However, this is, to stress it out, =E2=80=93 just my preference, =E2=80= =93 the very same thing that makes me disable global-font-lock-mode in Emacs, or to run Firefox with ECMAScript disabled (via NoScript) most of the time. And the sole justification I have for this first preference is that it allows me to write valid HTML documents which are =E2=80=93 at the very same time =E2=80=93 well-formed = XML. As for the software that I=E2=80=99m not the principal developer of, =E2= =80=93 I=E2=80=99d accept any output that does conform to the standards. [=E2=80=A6] > @key should be rendered as , possibly with an additional class. > Yes, even when inside @kbd =E2=80=94 HTML allows and encourages nesting > . No objection. > @t is a non-semantic command in Texinfo and should probably be > discouraged the same way has been discouraged in HTML since at > least 1997. It probably should become a styled with > .t { font-family: monospace }. > @verb is syntax sugar for escaping characters which have special > meaning in Texinfo, and has a non-semantic side effect of fixed-width > rendering. It probably should become a . Given that either command is probably currently used for code fragments anyway, using (possibly with a class) sounds like a better solution. [=E2=80=A6] > Note also that and /

nesting order are just the tip of the > iceberg. The wider problem is that the Texinfo HTML generator > generally assumes HTML =E2=89=883.2 even though it declares 4.01 > Transitional: =E2=80=A6 The question is: is it still necessary to offer HTML=C2=A03 compatibility in the generated documents? [=E2=80=A6] --=20 FSF associate member #7257 http://boycottsystemd.org/ =E2=80=A6 3013 B6A0= 230E 334A