Pedro Andres Aranda Gutierrez <[email protected]> writes:
> tell me how the ':font' property in org-latex-fontspec-config is not
> acceptable for you,
> while you have no problem in having it for polyglossia and babel. The
> current definitions are
>
> (latex-family :font ... :features ...) - in fontspec
> vs
> (language :variant ... :font :props ...) - in babel and polyglossia
I have the same problems with language (for reasons of uniformity).
Remember one of my earlier examples:
;; Default roman font for hindi, used instead of Source Code Pro
("Noto Serif Devanagari" :features "Script=Devanagari" :lang "hindi" :family
"rm")
Note how I also moved the language to :lang property.
> If you so much worry about uniformity, I would very willingly change
> :features for :props
> in org-latex-fontspec and split the fallback to
> (script :font ... :props ...)
> and then we would have exactly the same scheme which is acceptable for
> babel and polyglossia everywhere.
Having consistent naming is what I want yes. (I have no preference
whether we consistently use :features or consistently using :props everywhere)
> Merry Christmas, /PA
>
> PS: look at the last push with the modification of the docstring to see if
> it makes more sense to you now.
FONT-FAMILITY is better than FONT-NAME, yes. But this does not solve my
confusion about using font family vs script.
--
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>
