On 17/07/2025 16:02, Christian Moe wrote:
Max Nikulin writes:
I have noticed another case when "latex" in "#+begin_latex" is
rendered as subscript in a Worg article. Do you expect massive
regressions if subscript without explicit curly braces are suppressed?
[...]
org-contrib/babel/examples/drift.org: be the proportion of red individuals. So
X_1 is 6 and p_1 is 0.6. To
org-contrib/babel/examples/drift.org: individual. So X_2 is a /binomial/
random variable, with 10 trials and
Must be typed as \(X_1\), \(p_1\), and \(X_2\) to use proper font (italics).
org-hacks.org:hydrometer correction, abv calculation, priming sugar for a given
CO_2
This is a better example when subscript should be outside of LaTeX
fragment. I do not like that the manual contains an example with math
typed in plain text
<https://orgmode.org/manual/Subscripts-and-Superscripts.html>
(info "(org) Subscripts and Superscripts")
#+begin_example
exporters/freemind.org:out release_7.9.4/
exporters/xoxo.org:out release_7.9.4/
#+end_example
Thanks for fixing it.
So the objection I have is not about regressions, but about which
writing norm to require. I don't think there's a strong reason why
people should have to write =CO_{2}= instead of =CO_2=. And there's no
good reason for writing "release_7.9.4" in the above examples.
I think, it is acceptable to type "CO_{2}". However I would prefer to
recommend contributors to set ^:t for specific file to override
defaults. The file with "CO_2" has explicit "#+OPTIONS: ^:t"
However, there /is/ a good reason for the convention that one should use
verbatim markers when quoting keywords like =#+begin_src=. Failure to do
should be fixed, and export with subscripts is a useful tripwire that
should ideally help us to catch it.
My goal is to make formatting better for visitors. Mistakes during
editing of articles are unavoidable.
I think, the only way to find all improper use of sub/super-scripts is
to run org-element parser with t setting for all files and to report
found subscripts.
Whether or not we change the default, it might be a good idea to note
it in worg-editing.org.
I agree, but some decision is required before.
