From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Wiesner Subject: Re: HTML export and info: links Date: Wed, 3 Jul 2013 17:57:02 +0200 Message-ID: References: <87bo6nrzsh.fsf@bzg.ath.cx> <874ncc6pci.fsf@bzg.ath.cx> <87ip0s56ab.fsf@bzg.ath.cx> <87wqp83pvj.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UuPQX-0005jD-Ql for emacs-orgmode@gnu.org; Wed, 03 Jul 2013 11:57:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UuPQV-0000TL-Er for emacs-orgmode@gnu.org; Wed, 03 Jul 2013 11:57:05 -0400 In-Reply-To: <87wqp83pvj.fsf@bzg.ath.cx> 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: Bastien Cc: emacs-orgmode@gnu.org 2013/7/3 Bastien : > Sebastian Wiesner writes: > >> Ideally the HTML exporter would consult this database when exporting >> info links, to find out where the corresponding HTML manual is >> published. > > I see, thanks. Is it safe to assume that htmlxref.cnf will always > be located in /usr/share/texinfo/? E.g. is it for you? It's not actually located there at all. My Texinfo is installed via Homebrew into "~/.homebrew", hence my "htmlxref.cnf" is at "~/.homebrew/share/texinfo/htmlxref.cnf". There is no "/usr/share/texinfo/htmlxref.cnf". Texinfo doesn't read a single file anyway, but all of these, and merges them into a single file. For my manual, I use an additional "htmlxref.cnf" right next to the ".texi" source to add some missing links. The Org exporter should take all of these files, and merge them by the same rules. For system-wide configuration files, it should either try to get the right prefix out of the "makeinfo" executable in "exec-path" (as returned by "executable-find"), or take the list of files from a customization option. The latter is probably easier, and more predictable to the user. Implementing this likely amounts to a fair bit of work, which I was somewhat disappointed to learn that Org doesn't do it already :)