On 08/03/2024 22:44, Juan Manuel Macías wrote:
Max Nikulin writes:(org-export-string-as "Alpha@Beta{" 'html '(:export-options (body-only))) "<p>\nAlpha<span class=\"Beta\"></span>{</p>\n" (org-export-string-as "Alpha@Beta[" 'html '(:export-options (body-only))) Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)Maybe in that case you could add a zero width space character. In any case, if someone has reasons to write "Alpha@Beta{" they may also have reasons to write "Alpha_Beta": (org-export-string-as "Alpha_beta" 'html '(:export-options (body-only))) <p> Alpha<sub>beta</sub></p>
From my point of view it is a pitfall with Org syntax, but parser works as it should.
On the other hand if there is no closing bracket then it is not an inline special block, so this part of document should be considered as text (unless some other objects are recognized).
Currently Org parser does not signal errors even for invalid input.
