Pedro Andres Aranda Gutierrez <[email protected]> writes:
>> To Pedro: No, it would not mean a complete rewrite of everything. You
>> can simply pre-process the variable value to expand into lower-level
>> format. Then, pass it to the existing functions. No rewrite needed. Just
>> some extra function to be written: not now; later.
>
> That was not what I was reading from your messages. If it is to be made
> later and it doesn't interfere the process, why not.
I was talking specifically about font sets.
Actually, I did not want to bring that topic yet. I did not anticipate
that default font for all scripts would require introducing font
sets. That's simply my lack of understanding of how LaTeX fonts work.
> A side comment with a use-case:
> I'd rather work on something more fundamental like adding a markup for
> inlined text to be typeset in sans (versus normal) font.
> This would be useful for LaTeX and HTML that I can think of. There are
> instances where you typeset your document in normal font
> and use sans font to include and highlight specific terms in other
> languages (ie. Latin) in a not too intrusive way.
> Having that makes inlining \textsf{} unnecessary. Forgive me if I'm wrong,
> but that doesn't export nicely to HTML, does it?
That would certainly be welcome. Inline special blocks feature that
would be relevant is stalled.
However, before that, I would like to make the feature branch into a
state that I deem minimal for the merge.
>> Well. Such people could as well use #+LATEX_HEADER. I think that it is
>> very important to lower the entry barrier for latex configuration.
>>
> When I point people at some EmacsConf presentations and they see the file
> headers with the LATEX_HEADERs, they just refuse to use Org.
> This is my humble contribution to lowering the entry barrier.
How it is different from dir-locals?
Remember that all those #+LATEX_HEADER lines can be trivially
#+INCLUDEd to the same effect.
>> That's why I am pushing to simplify the font-config values.
>>
> But they are already in a bare minimum. Simplifying further means
> losing features and, I fear, use cases.
I think I confused you by suggesting the default font idea. (Alas, it is
not trivial at all, in contrast to what I thought).
The variable value format I am suggestion does not require losing any
features. It is merely re-shaping the value into a simple list instead
of nested. You do not even have to remove the :tag option.
Please examine the example I sent in another message.
--
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>
