From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] Add "latex" option to ox-bibtex.el Date: Sat, 13 Jul 2013 10:41:02 +0200 Message-ID: <87ehb297j5.fsf@gmail.com> References: <87vc4g83po.fsf@gmail.com> <87ip0f99yq.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32793) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UxvNr-0007qE-0T for emacs-orgmode@gnu.org; Sat, 13 Jul 2013 04:40:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UxvNq-0007S6-0o for emacs-orgmode@gnu.org; Sat, 13 Jul 2013 04:40:50 -0400 Received: from mail-wg0-x235.google.com ([2a00:1450:400c:c00::235]:64659) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UxvNp-0007S2-Pf for emacs-orgmode@gnu.org; Sat, 13 Jul 2013 04:40:49 -0400 Received: by mail-wg0-f53.google.com with SMTP id y10so8902715wgg.20 for ; Sat, 13 Jul 2013 01:40:48 -0700 (PDT) In-Reply-To: (feng shu's message of "Sat, 13 Jul 2013 07:15:34 +0800") 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: feng shu Cc: "emacs-orgmode@gnu.org" Hello, feng shu writes: > I want to add a option which can setting bib for html export and latex > export separately, > As it for the reason: > 1. bibtex2html can't work well with complex bib style, so using a simple > style and making it > show correctly is reasonable choose, > 2. bibtex2html can't find bib style in current dir, for example > (./file.sty) , > 3. the biblatex user. I understand that. Though, you didn't tell me what was wrong with the hook I provided. > In my opinion, the solution seemd more hacky than mine for a user, Of course. A hook (or a filter) is a hack. But at least, it doesn't live in core. > It let my org-mode file more unportable. Portability is not an issue here. If you're really worried about it, you need to share your configuration file along with your Org documents anyway. If you don't, your documents will never be totally portable. > Could you share you opinion and reason about my approach: Is the idea , > separating with a new option, hacky? or my code hacky? . My opinion is that we cannot add options to handle every possible use case. That's why filters and hooks exist in the first place. Thus, when a feature can be implemented in a couple of lines with a hook/filter, I just ask to think twice before adding it to core. Now, speaking about the patch, you only provide an option to ignore "bibliography" keyword when exporting with latex back-end, but you still have to write correct bibliography command by hand in the Org buffer. I think a cleaner solution would be to be able to choose both bibliography and style according to back-end from within the keyword itself. I very much like Babel's "by-backend" approach. That's more work for sure, but, meanwhile I think something like the hook I provided is good enough for the job at hand. What do you think? Regards, -- Nicolas Goaziou