Pedro Andres Aranda Gutierrez <[email protected]> writes:
> Would you please restate your questions.
> I'm lost in the thread.
I suggested the following alternative format for font-config variable:
(setopt
org-latex-babel-font-config
'(;; Default "rm" font
("Source Code Pro" :features "Scale=MatchLowercase" :family "rm")
;; Default mono font
("DejaVu Sans Mono" :features "Scale=MatchLowercase" :family "tt")
;; Default roman font for hindi, used instead of Source Code Pro
("Noto Serif Devanagari" :features "Script=Devanagari" :lang "hindi" :family
"rm")
;; Default monospace font for hebrew, used instead of DejaVu Sans mono
("Noto Mono Hebrew" :features "Script=Hebew" :lang "hebew" :family "tt")))
>> I believe that the above is much easier to understand for users compared
>> to nested alists we have now.
>>
> But then you lose the structure and it gets much more complex to add things
> on a language base to a common configuration.
> Fontspec is already alist based, so let's keep that uniformly expressed.
Nested alist-based values are always hard to work with for users. I know
it from many complaints about capture templates.
I am not sure if I understand what you mean by more complex. Can you
provide an example that would be simpler using the existing configuration?
--
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>
