Pedro Andres Aranda Gutierrez <[email protected]> writes:
>> >> Also, since we now allow multiple languages to be listed in #+LANGUAGE,
>> >> we may need to update the manual when talking about #+LANGUAGE keyword
>> >> in other places as well; not just in latex export section.
>> You seemingly did not address this comment.
>
> I've gone through the code once again and I think we need to start
> looking at places where #+LANGUAGE is used outside the LaTeX exporter.
> There we will need to filter out and keep the first language if we
> find a comma separated list of languages...
>
> WDYT?
1. It will be better to use space instead of comma. Then, we will be
able to use "split" directive in `org-export-options-alist'
2. We will probably need to do some backwards compatibility refactoring,
making sure that no extra package using :language is broken.
Preliminary, I am thinking of the following approach:
(i) We introduce a new :languages export option
(:languages "LANGUAGE" nil (list org-export-default-language) split)
(ii) We introduce pre-processing into `org-export--annotate-info'
extracting the first language from :languages property into
:language. That way, everything relying on :language value being
a single string, will remain operational. Newer code can then
use :languages directly.
WDYT?
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
