Pedro Andres Aranda Gutierrez <[email protected]> writes: > Do you /really/ want to go this path??? > > I'd rather keep this out of scope and make people request > support @polyglossia, @babel or @listings: > > 1. If you go through the 42 pages of > https://latex.org.uk/language/babel/contrib/hebrew/hebrew.pdf you will see > that listings are mentioned nowhere. > 2. If you go through the 241 pages of > https://texdoc.org/serve/listings.pdf/0, you will see Hebrew only mentioned > once in relation with the use of characters and there is no mention of the > use of listings in RTL.
For me, it looks like people just have to do it manually as for now. Anyway, I think this is getting too complex, and lower priority than merging the branch. So, let's move on. (Meanwhile, I just open RFC where we can discuss the topic in more details, without linking it to your branch) The next topic I'd like to discuss further before we merge is variable value formats for org-latex-fontspec-config, org-latex-polyglossia-font-config, and org-latex-babel-font-config. Let me first provide my high-level understanding (maybe still wrong; let me know) about how these 3 variables work: 1. org-latex-fontspec-config has no idea about the notion of language. All it knows is font scripts: main (roman/serif/rm), sans (sf), math, and mono (tt), possibly also CJK/JP variants of main/sans/mono. For each script, we can define font + features, and one or ore fallback fonts. 2. org-latex-polyglossia-font-config gets more complex. It knows about languages and falls back to fontspec-config when language-specific font is not defined. For each language, again, font + features can be defined. By default, given a language + font, that font will be used to typeset everything in that language - main text, emphasis, and monospaced fragments. However, if :variant is provided (rm/sf/tt), user can specify individual fonts for main text, emphasis, and monospaced fragments in that language (is it really true? I think this is not how it works in the code, but what I say here seems reasonable) There is also :tag, but I do not quite understand its purpose. Can you please explain? (Reading the manual did not help) 3. org-latex-babel-font-config is similar to polyglossia-font-config. It also maps language to font + features, but with a twist. Unlike, polyglossia-font-config, you cannot just say - use the same font famility for normal, emphasized, and monospaced text. You must always specify individual font + features for each rm/sf/tt script. In addition, it is possible to explicitly specify default font used for languages other than with explicitly specified font settings. (is this really accounteed for in the code?) -- 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>
