From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: [RFC] Org version of the Org manual Date: Tue, 05 Mar 2013 17:14:22 -1000 Message-ID: References: <87ehfuonx6.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:47888) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UD4oh-0006Hw-QF for emacs-orgmode@gnu.org; Tue, 05 Mar 2013 22:14:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UD4og-00007j-Ep for emacs-orgmode@gnu.org; Tue, 05 Mar 2013 22:14:55 -0500 Received: from oproxy13-pub.unifiedlayer.com ([69.89.16.30]:48454) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1UD4og-00007Y-6P for emacs-orgmode@gnu.org; Tue, 05 Mar 2013 22:14:54 -0500 In-Reply-To: <87ehfuonx6.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 04 Mar 2013 22:28:05 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Hi Achim, Achim Gratz writes: > Thomas S. Dye writes: > [=E2=80=A6] >> I look forward to picking this project up again in a week or so, or >> learning from my Org colleagues that the project ought to be scuttled. > > Hi Tom, > > this looks good. Thanks for reviewing a work in progress. I'm really pleased it looks good to you. > > I've implemented a rough draft of a Makefile that integrates with the > build system (a clean target is still missing, etc.pp.). To use, clone > orgmanual.git in the Org worktree (don't add it, or add as a submodule), > then drop this Makefile into orgmanual/: These instructions assume more knowledge than I have. Could you be more specific about "in the Org worktree"? Should I create a branch where I do this? Or, should I put this in one of the upstream branches and arrange to push it into the Org repo? In any case, can you suggest a location? /contrib? /doc? > > BEXP=3D$(BATCH) \ > --eval '(add-to-list '"'"'load-path "../lisp")' \ > --eval '(setq org-footnote-auto-adjust nil)' \ > -l ox-texinfo \ > --eval '(add-to-list '"'"'org-export-snippet-translation-alist '"'"'("in= fo" . "texinfo"))' > ORG2TEXI=3D-f org-texinfo-export-to-texinfo > ORG2INFO=3D--eval "(org-texinfo-compile \"./$<\")" > > orgmanual.texi: orgmanual.org > $(BEXP) $< $(ORG2TEXI) > orgmanual.info: orgmanual.texi > # $(BEXP) $< $(ORG2INFO) > $(MAKEINFO) --no-split $< -o $@ > orgmanual.pdf: LC_ALL=3DC # work around a bug in texi2dvi > orgmanual.pdf: LANG=3DC # work around a bug in texi2dvi > orgmanual.pdf: orgmanual.texi > $(TEXI2PDF) $< This seems straightforward. > > Also make a link (for now) to ../doc/org-version.inc and add this to > local.mk: > > .PHONY: orgmanual > orgmanual: > $(MAKE) -C $@ $@.info $@.pdf > I can do this, but then the orgmanual.info generated from the source will indicate the wrong version. Is that OK? I have instructions from Bastien how to cull all the changes to org.texi that have taken place since I started translating the manual to org several months ago. When I'm done going through those, then the link will indicate the correct version. > > A "make orgmanual" then exports to orgmanual.texi (slowly) and an info > file is produced by makeinfo, but texi2dvi does not want to produce a > PDF yet and errors out. The info file contains a few easily spotted > mistakes in the macro section like "~@{@{@{name(arg1,arg2)@~@}@}}" that > are quite probably the source of some of these errors. Thanks, I found these and have corrected them. There are probably more ... All the best, Tom --=20 Thomas S. Dye http://www.tsdye.com