On Mon, 30 Jun 2025 at 19:34, Ihor Radchenko <yanta...@posteo.net> wrote:
>
> Pedro Andres Aranda Gutierrez <paag...@gmail.com> 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)
If I get you right, :languages will be an array, right?
>    (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?

Thx, /PA
>
> --
> 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>



-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Sagen's Paradeiser, write BE!
Year 1 of the New Koprocracy

Reply via email to