From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Gavin Smith Newsgroups: gmane.comp.tex.texinfo.bugs,gmane.emacs.devel Subject: Re: texi2html output validity Date: Tue, 23 Dec 2014 18:14:01 +0000 Message-ID: References: <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> <20141223164911.GD5623@free.fr> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1419358456 31435 80.91.229.3 (23 Dec 2014 18:14:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Dec 2014 18:14:16 +0000 (UTC) To: Patrice Dumas , Yuri Khan , Texinfo , Emacs developers Original-X-From: bug-texinfo-bounces+gnu-bug-texinfo2=m.gmane.org@gnu.org Tue Dec 23 19:14:07 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 1Y3TyB-0003s2-B6 for gnu-bug-texinfo2@m.gmane.org; Tue, 23 Dec 2014 19:14:07 +0100 Original-Received: from localhost ([::1]:45765 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3TyA-0004nn-2o for gnu-bug-texinfo2@m.gmane.org; Tue, 23 Dec 2014 13:14:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44276) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3Ty7-0004nd-GN for bug-texinfo@gnu.org; Tue, 23 Dec 2014 13:14:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y3Ty6-0008QO-LN for bug-texinfo@gnu.org; Tue, 23 Dec 2014 13:14:03 -0500 Original-Received: from mail-ig0-x235.google.com ([2607:f8b0:4001:c05::235]:36412) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3Ty6-0008Q2-GI; Tue, 23 Dec 2014 13:14:02 -0500 Original-Received: by mail-ig0-f181.google.com with SMTP id l13so6303009iga.2; Tue, 23 Dec 2014 10:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bT/8y50lXIFeTowk9xn7PoNZuEum/7+Y7r4UxH8wmHw=; b=XlK7U6ve00mLJ+TRV5p5po0PjHhMqKheAEQqKUIR6FqIJD5RY5bDIHx3RURTq5nvVp 5dcGQnddqGrgEeSmfjPRGS+AqSV8cBIDkndkm0vyNsshDErKEnqh4T9pXCxPiuOCdoXh YxwkQ4DYritPhHBlnRUY1EZ/e5Jze1c/hGTldLQBXmzTomXUCTrVv6V7YUgexpdPwT84 lclbDsOq2MPHLLkl4ZUu+B6bUzxtnoDZQ5FOdoiIw8UNaqqXSAKb4Gt3Nh6y/55+E/K+ 5amkXxpH8YZyJ17xBm7dxAyZv8l+eluLH7DHWH3I8FXBLrGyZp2Wg2O+IULuu+ok4OVl JYhw== X-Received: by 10.42.107.211 with SMTP id e19mr22447843icp.27.1419358441782; Tue, 23 Dec 2014 10:14:01 -0800 (PST) Original-Received: by 10.107.170.231 with HTTP; Tue, 23 Dec 2014 10:14:01 -0800 (PST) In-Reply-To: <20141223164911.GD5623@free.fr> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c05::235 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:6986 gmane.emacs.devel:180587 Archived-At: On Tue, Dec 23, 2014 at 4:49 PM, Patrice Dumas wrote: > First of all it is a bit unclear where this html comes from. In > general, both texi2html and texi2any/makeinfo, especially for makeinfo > starting at version 5 render properly nested html tags. > Could it be coming from some HTML output customization that is used for the Lilypond manuals? >> @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 }. > > @t and other non-semantic commands are already discouraged in the manual. > But I see no point in not using for @t, as long as browser support > it (which is likely to be until the end of times). CSS is not supported > by every browser. Using a class and CSS for instead of would not make the output file any more "semantic", it just specifies a fixed-width font in a more verbose way. I would say if you don't like appearing because it is deprecated, consider also the @t command deprecated. It's fine to produce "bad" (non-semantic) output for "bad" input.