Answers inline. On Sun, 23 Nov 2025 at 10:30, Ihor Radchenko <[email protected]> wrote:
> Pedro Andres Aranda Gutierrez <[email protected]> writes: > > > Hi Max, list, > > ... > > Currently, things are lower level. > > Note to Max: We have discussed the idea of fontsets in one of the > branches. That's a nice idea, but I do not think that we have to do it > before merging the branch. > > > That would mean a complete rewrite of everything... > > > If something more high level is needed, it could build on the feature > > branch, not replace it. > > 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. 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? > ... More on my thought process. > > > > My (maybe candid) expectation was that people using the LaTeX exporter > > would be aware that they use a LaTeX engine below Org mode. > > They need to be, if they want choose, for example, the right package to > > handle their linguistic needs. > > I was expecting people to inform themselves enough to understand the > > differences between the babel and the polyglossia package to make the > right > > choice. Or at least to understand why the project they are working on has > > made a concrete choice and what the implications are. > > 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. > 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. > -- > 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> > -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler "Sagen's Paradeiser" (ORF: Als Radiohören gefährlich war) => write BE! Year 1 of the New Koprocracy
