Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes:
>> 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)
> If I get you right, :languages will be an array, right?
A list.
>> (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?
> My concern is the impact it might have for other backends...
>
> Let's go through a use case:
>
> Say you have an Org document you want to export to PDF and HTML from Org.
> Your Web page needs to be in Italian, and you want to have ancient
> Greek text on it.
> To produce the PDF, you intend to use =polyglossia=.
>
> What would be the approach?
#+LANGUAGE: it el
#+LATEX_MULTI_LANG: polyglossia
That will translate to INFO containing
:language "it" :languages ("it" "el") :latex-multi-lang "polyglossia"
That said, I just found
https://list.orgmode.org/orgmode/87edizahiu.fsf@localhost/
We may need to think about that discussion before finalizing things.
--
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>
