Pedro Andres Aranda Gutierrez <[email protected]> writes:
> You are right in that it controls language detection, punctuation, etc. So
> we have two 'groups of settings' for babel that you map to a language (from
> #+LANGUAGES). I find it more convincing to go this way, because it is more
> 'grow as you go'.
>
> To tell you the truth, I will never use this myself, because I have more
> than enough with fontspec and \usepackge[language]babel (or polyglossia).
>
> So, you want it the other way round, it's back to the drawing board,
> rewrite the babel support code and the parts relating to this in
> org-manual.org
Right. But I also raised this point earlier.
I still think that the values are way too complex. They are definitely
complex for me, even though I have some experience with LaTeX.
>> IMHO, it is worth it in this case. Simply because babelprovide is not
>> really about fonts, maybe except onchar in particular, but that's rather
>> an exception. What about adding org-latex-babel-language-config variable
>> for babelprovide and potentially other options?
>
> What other options do you see? If I read you correctly, this variable would
> be a list of plists, linking
>
> (<lang from #+LANGUAGES> :provide <string or list of strings>)
Yes, something like this.
For other options, things like shorthands, babelhyphenation, digits, etc.
We do not really need to implement them now. :provide is enough. But
others can be added if users ask for them.
>>> If it weren't for that, I could live with a flatter version à la
>> ...
>> Yup, it is more appealing to me. Moreover, it has a potential to merge
>> all font-related settings into a single customization. After all, what
>> are chances that you would need different fonts for the same language
>> for babel vs. polyglossia?
>
> Contributions to conferences vs. book chapters, for example. Has happened
> to me.
Could you elaborate? Your example is a documentclass. How does it have
anything to do wrt babel vs. polyglossia?
>> And even if you do have to do such thing, we
>> can always have an extra property as in `org-latex-packages-alist' to
>> limit which compilers a given font should apply to.
>
> I can't follow you here... And that should be easier to configure/customise
> for the end user?
Imagine a single customization like `org-latex-fonts'.
Users can then
;; For all compilers
(push '("CMU Serif" :family "sf") org-latex-fonts)
(push '("Noto Sans Mono" :family "tt") org-latex-fonts)
;; Just for babel
(push '("Noto Serif" :family "sf" :package "babel") org-latex-fonts)
;; Just for ja + babel
(push '("Noto CJK" :lang "ja" :family "rm" :package "babel") org-latex-fonts)
--
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>
