From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: On being web-friendly and why info must die Date: Wed, 10 Dec 2014 20:47:21 +0100 Message-ID: <87r3w7b83a.fsf@wanadoo.es> References: <20141205123549.GA29331@thyrsus.com> <87lhmlncb1.fsf@earlgrey.lan> <20141205193643.GB5067@thyrsus.com> <87tx19rd1b.fsf@fencepost.gnu.org> <20141205215138.GF7784@thyrsus.com> <54823617.4000406@cs.ucla.edu> <83k325195l.fsf@gnu.org> <5482D94B.2070102@cs.ucla.edu> <5484FF31.5010808@cs.ucla.edu> <5485FC59.5030700@cs.ucla.edu> <87388p6glt.fsf@engster.org> <871to9lw6g.fsf@fencepost.gnu.org> <5486A704.6090305@cs.ucla.edu> <87k321jj4e.fsf@fencepost.gnu.org> <54876F7F.9000607@cs.ucla.edu> <87y4qfj2u9.fsf@fencepost.gnu.org> <54889A57.5060905@cs.ucla.edu> <87vbljb9f4.fsf@wanadoo.es> <54889F6D.6060408@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1418240879 24963 80.91.229.3 (10 Dec 2014 19:47:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 10 Dec 2014 19:47:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 10 20:47:52 2014 Return-path: Envelope-to: ged-emacs-devel@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 1XynEm-00029y-6a for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2014 20:47:52 +0100 Original-Received: from localhost ([::1]:47676 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XynEl-0006N6-RZ for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2014 14:47:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33506) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XynEd-0006Mf-Ca for emacs-devel@gnu.org; Wed, 10 Dec 2014 14:47:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XynEX-0006Gt-EP for emacs-devel@gnu.org; Wed, 10 Dec 2014 14:47:43 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:40778) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XynEX-0006G0-7d for emacs-devel@gnu.org; Wed, 10 Dec 2014 14:47:37 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XynEW-00021a-7h for emacs-devel@gnu.org; Wed, 10 Dec 2014 20:47:36 +0100 Original-Received: from 129.red-88-10-128.dynamicip.rima-tde.net ([88.10.128.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Dec 2014 20:47:36 +0100 Original-Received: from ofv by 129.red-88-10-128.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Dec 2014 20:47:36 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 20 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 129.red-88-10-128.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:25Xkybj2mGayMMN4uDFbCTxBleU= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:179695 Archived-At: Paul Eggert writes: > That should catch some problems, but it's not enough. Typically I > focus on that editing the .texi file first to get the content right. > Then, I want to make sure the result is readable so I generate the > output and look at it. I reckon that those issues are related to the texinfo format, specifically. Other formats can be checked for readability without exporting them first. > Problems with looks often include > fairly-mundane things like a capitalized word at sentence end which > messes up later spacing, things which one can easily see when looking > at the info output, but which one can't easily expect a text editor to > catch. Isn't it possible to defer those issues to an advanced stage where the areas with documentation changes are checked ``en-masse'' instead of checking one change at a time?