Re: [PATCH] Add "latex" option to ox-bibtex.el

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

feng shu <tumashu@gmail.com> 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