"Sebastien Vauban" <wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org> writes:
> Nicolas Goaziou wrote: >> I used: >> >> (add-to-list 'org-entities-user '("omacr" "\\={o}" nil "ō" "o" "o" "ō")) >> >> without a problem. > > IIUC, you specify how to translate some "LaTeX-like command" to the different > back-ends. But I don't see DocBook nor OOo in the list: > > ┏━━━━ > ┃ User-defined entities used in Org-mode to produce special characters. > ┃ Each entry in this list is a list of strings. It associates the name > ┃ of the entity that can be inserted into an Org file as \name with the > ┃ appropriate replacements for the different export backends. The order > ┃ of the fields is the following > ┃ > ┃ name As a string, without the leading backslash > ┃ LaTeX replacement In ready LaTeX, no further processing will take > place > ┃ LaTeX mathp A Boolean, either t or nil. t if this entity needs > ┃ to be in math mode. > ┃ HTML replacement In ready HTML, no further processing will take > place. > ┃ Usually this will be an &...; entity. > ┃ ASCII replacement Plain ASCII, no extensions. Symbols that cannot be > ┃ represented will be left as they are, but see the. > ┃ variable `org-entities-ascii-explanatory'. > ┃ Latin1 replacement Use the special characters available in latin1. > ┃ utf-8 replacement Use the special characters available in utf-8. > ┃ > ┃ If you define new entities here that require specific LaTeX packages to > be > ┃ loaded, add these packages to `org-export-latex-packages-alist'. > ┗━━━━ > > Aren't those backends missing? Or do I miss how it really is used? I think most back-ends understand at least one of the formats used in this alist. For example the DocBook one just reads HTML entry. Regards, -- Nicolas Goaziou