Nicolas Goaziou <n.goaz...@gmail.com> writes:
> Hello,
>
> Bastien <b...@altern.org> writes:
>
>> Hi Andreas and all,
>>
>> Andreas Leha <andreas.l...@med.uni-goettingen.de> writes:
>>
>>> Eric suggested/uses this format (thanks for sharing, Eric):
>>> [[cite:jones-etal-2000][Jones et al., 2000]]
>>> ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^
>>> key displayed in org
>>
>> I'd suggest to treat org-link-abbrev-alist and locally defined
>> abbreviated links differently when opening the link at point and
>> when exporting the buffer.
>>
>> At expand time, the exporter could attach a list of export functions
>> (filters?) to the expanded link, depending on the local setting for
>> the abbreviated link or `org-link-abbrev-alist'. For example:
>>
>> #+LINK: cite file:my.bib::%s org-latex-bibtex-link
>>
>> (setq org-link-abbrev-alist
>> '(("cite" "file:my.bib::%s" 'org-latex-bibtex-link)))
>>
>> Then org-latex-bibtex-link would internally find the link, process
>> the BibTeX entry and return a sensible \cite{...} string.
>>
>> What do you think?
>
> If we're not going to provide a multi-backend solution, I suggest to
> keep things simple and write LaTeX code directly (or use the solution
> provided by Eric). Unless you have something else in mind with these
> link abbrevs, of course.
>
I agree. Getting 'simple' \cite or better [[cite: ]] links to export in
other backends than LaTeX only should be the first step, anyway.
Regards,
Andreas
