ndwarshuis
/
org-mode
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

org-manual: Stick to typographic conventions 

* doc/org-manual.org (Subscripts and Superscripts): Use ~...~ markup
for symbols and capital letters for keywords. Also prefer direct voice
and present tense whenever possible.
This commit is contained in:
Nicolas Goaziou 2020-02-20 09:57:38 +01:00
parent 6de5bcee87
commit 5d2075abad
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/org-manual.org
View File

@ -10701,9 +10701,9 @@ change this convention. For example, when setting this variable to
~{}~, =a_b= is not interpreted as a subscript, but =a_{b}= is.
You can set ~org-use-sub-superscripts~ in a file using the export
option =^:= (see [[*Export Settings][Export Settings]]). For example, =#+options: ^:{}=
sets ~org-use-sub-superscripts~ to ='{}= and only the curly bracket
notation of super- and subscripts will be used.
option =^:= (see [[*Export Settings][Export Settings]]). For example, =#+OPTIONS: ^:{}=
sets ~org-use-sub-superscripts~ to ~'{}~ and limits super- and
subscripts to the curly bracket notation.
You can also toggle the visual display of super- and subscripts:
@ -10716,7 +10716,7 @@ You can also toggle the visual display of super- and subscripts:
#+vindex: org-pretty-entities
#+vindex: org-pretty-entities-include-sub-superscripts
Set both ~org-pretty-entities~ and
~org-pretty-entities-include-sub-superscripts~ to =t= to start with
~org-pretty-entities-include-sub-superscripts~ to ~t~ to start with
super- and subscripts /visually/ interpreted as specified by the
option ~org-use-sub-superscripts~.