Formatting in Acronyms

[anonymous]

Is it possible to have a formatted acronym, like A³?

[anonymous]

What about CamelCase Acronyms? I have to use CamelCase or CamelCase in the text in order to be displayed correctly (not as a link to wiki:CamelCase), but then the word is not identified by the plugin as an acronym.

[morpheus.me@…]

Another problem/request: (I also posted the previous two) I have already defined an acronym XXX and would like to add another one, YYY-XXX, but it seems that the hyphen confuses the plugin, and the result is that the YYY-XXX acronym is not recognised. Instead in every occurance of YYY-XXX the XXX part is recognised and linked to the XXX acronym URL. I know I may be asking a lot, so please let me know if (and when) are you going to add/correct these functions. Other than that great plugin, keep up the good work! Thanx!

[Ryan J Ollos]

Replying to morpheus.me@gmail.com:

Another problem/request: (I also posted the previous two) I have already defined an acronym XXX and would like to add another one, YYY-XXX, but it seems that the hyphen confuses the plugin, and the result is that the YYY-XXX acronym is not recognised. Instead in every occurance of YYY-XXX the XXX part is recognised and linked to the XXX acronym URL.

Confirmed. However, we should have a separate ticket for that issue. See #8266.

[Ryan J Ollos]

Replying to anonymous:

What about CamelCase Acronyms? I have to use CamelCase or CamelCase in the text in order to be displayed correctly (not as a link to wiki:CamelCase), but then the word is not identified by the plugin as an acronym.

This is a request for a separate ticket. See #8267.

[Ben Allen]

For something as simple as the "A cubed" example in the ticket description, you can use the Unicode "superscript three" character instead of using wiki formatting to achieve the same effect. That's what I do for the acronym "I²C" on our wiki. It makes the acronym a bit more annoying to type, but sometimes copying and pasting text into the wiki from other programs will result in these kind of Unicode characters being used so YMMV.

[Steffen Hoffmann]

I confirm, that 0.11 branch (0.2dev) works exactly for the requested case with Unicode chars, due to the regexp change in [9662] for #8266. But of course this is merely a workaround, i.e. not applicable to any subscript and non-numerical or higher order superscript.