• Anonymous User 13812167

    (@anonymized-13812167)


    Let say I write:

    \( a<c \)
    
    [caption ...]<img ...> My figure[/caption]

    Caption shortcode is not processed. But if I change the code to:

    \( a>c \)
    
    [caption ...]<img ...> My figure[/caption]

    Caption shortcode is processed as usual. The only difference is that I have changed < to >.

    A similar problem occurs if I just use: [latex]a<c[/latex]. WP sees that as a single “empty” shortcode (just [latex]) and some unrelated text (namely the a<c[/latex] part) afterwards. Changing < to > once again “solves” the issue.

    So I believe there are some problems with HTML cleanup and Shortcode API. I believe these problems might be related to fixes of Shortcode API done in 4.2.3.

    So far I can bypass the problem by changing < into <, but this is not proper LaTeX.

Viewing 1 replies (of 1 total)
  • Yes, quite possibly a bug. Though I am sure that you will get into arguments here, working from the understanding that the text is actually HTML source code, then the first example is ill formed in having an inbalanced block that starts with < but does not close.

    A strictly correct html usage would use codes such as & lt; (no space) for less than and & gt; for greater than. This is indeed a pain, even getting my text in this response to look like I intended has caused me to edit it, here is hoping. For the third time!

Viewing 1 replies (of 1 total)
  • The topic ‘Shortcode issue with less-than sign’ is closed to new replies.