Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes:
> Attached is a new version of the multi-lingual demo ZIP.
>
> Thanks for testing, /PA
Looks good!
I think the remaining lualatex warnings (about missing languages and
hyphenation patterns) are all down to things missing from my texlive
installation, not problems with your code. Also tried adding Cyrillic
(Russian, Serbian) to the mix.
Side notes:
- I wonder how I would to configure things, exactly, if for some reason
I wanted to mix Latin-script Serbian and Cyrillic-script Serbian in
the same document.
- The test doc behaves a bit unexpectedly, in that the block quotes used
as a workaround for defining language environments are not
block-quoted. That is,
: #+ATTR_LATEX: :environment Arabic
: #+BEGIN_QUOTE
is not exported with \begin{quote}, only with \begin{Arabic}. Note
that special blocks like ~#+BEGIN_Arabic~, etc., can be used to the
same effect with less typing, and allow nesting exportable
~#+BEGIN_QUOTE~ environments inside them.
- But (though it may exceed the scope of your project) I hope we
eventually get a way to define language environments with `inline
special blocks' or the dedicated `inline language blocks' discussed
here: https://list.orgmode.org/87msrudgcn....@posteo.net/. It would
also be nice for Org to always be aware of such environments, e.g. to
use the appropriate smart quotes.
- It would also be nice if we could rely on a single naming system for
languages in Org regardless of backend -- preferably, in my view, if
we could use only the language shortcodes already used by Org, and
have Org translate them to the language names expected by Polyglossia,
so we don't need to remember them (including quirks such as
capitalizing Arabic).
Yours,
Christian
