You will see new SUB and SUP buttons in the post editor. These create subscripts and superscripts in the obvious manner.
This is considered preferable to using the unicode characters which are (or look like) superscripts or subscripts, which I have previously promoted using, via WinCompose sequences.
[Edit: There are now also short forms for these, namely [r] for radix (subscRipt) and [p] for power (suPerscript), as described here: viewtopic.php?f=15&t=497]
New [sub]...[/sub] and [sup]...[/sup] BBCodes
- Dave Keenan
- Site Admin
- Posts: 2180
- Joined: Tue Sep 01, 2015 2:59 pm
- Location: Brisbane, Queensland, Australia
- Contact:
- cmloegcmluin
- Site Admin
- Posts: 1700
- Joined: Tue Feb 11, 2020 3:10 pm
- Location: San Francisco, California, USA
- Real Name: Douglas Blumeyer (he/him/his)
- Contact:
Re: New [sub]...[/sub] and [sup]...[/sup] BBCodes
Testing, testing, 123...
The WinCompose versions are still extremely nice to have in situations lacking super- and sub-script capacity, such as in the prime factored forms of Sagittal comma names in spreadsheet settings, so thanks again for turning me on to those. But on the forum I'll stick to these BBCodes.
By the way — I don't know about others, but I can't help but pronounce them "BBC Codes." I'm sorry, but if you stick two capital B's and a capital C in sequence together, you've got the BBC.
The WinCompose versions are still extremely nice to have in situations lacking super- and sub-script capacity, such as in the prime factored forms of Sagittal comma names in spreadsheet settings, so thanks again for turning me on to those. But on the forum I'll stick to these BBCodes.
By the way — I don't know about others, but I can't help but pronounce them "BBC Codes." I'm sorry, but if you stick two capital B's and a capital C in sequence together, you've got the BBC.
- cmloegcmluin
- Site Admin
- Posts: 1700
- Joined: Tue Feb 11, 2020 3:10 pm
- Location: San Francisco, California, USA
- Real Name: Douglas Blumeyer (he/him/his)
- Contact:
Re: New [sub]...[/sub] and [sup]...[/sup] BBCodes
You may be interested to know that searching by R² in the browser still turned up R2 as a hit. So they are treated as equivalent at least by that tool.
- Dave Keenan
- Site Admin
- Posts: 2180
- Joined: Tue Sep 01, 2015 2:59 pm
- Location: Brisbane, Queensland, Australia
- Contact:
Re: New [sub]...[/sub] and [sup]...[/sup] BBCodes
That's great. Thanks. Apparently, they are both treated as equivalent to "R2". But the search-term hilighting algorithm fails to find R² or R2.cmloegcmluin wrote: ↑Wed Jun 17, 2020 2:45 pm You may be interested to know that searching by R² in the browser still turned up R2 as a hit. So they are treated as equivalent at least by that tool.
Warning: Everything from here on, in this thread, is completely off-topic.
Your "BBC codes" thing brings up a whole spiel of mine on what constitute sensible rules for lowerCamelCase and UpperCamelCase. The result of which is that the above should be written "BbCodes". Oh wait, that looks like "B flat codes". So, better as "bbCodes". But hey, I don't get to decide that. Here's the spiel:
I (and many others) believe that -case identifiers should never contain two consecutive uppercase letters (unless they are part of a hexadecimal number that ends the identifier), so as to prevent ambiguity as to where the word breaks are. This requirement is met by applying the following rules:
- Acronyms and initialisms must be treated the same as ordinary words, by having at most their first letter capitalised.
- Single-letter words (including abbreviations, acronyms and initialisms) must not be used, except as the last letter of an identifier or as the first letter of a lower-camel-case identifier.
- Because decimal digits are tall like uppercase letters, but have no lowercase form, a string of digits may only appear at the end of an identifier. This includes hexadecimal digits which should be in uppercase only.
- cmloegcmluin
- Site Admin
- Posts: 1700
- Joined: Tue Feb 11, 2020 3:10 pm
- Location: San Francisco, California, USA
- Real Name: Douglas Blumeyer (he/him/his)
- Contact:
Re: New [sub]...[/sub] and [sup]...[/sup] BBCodes
You’ll be happy to learn then, that I am already following these good practices in the code:
https://github.com/cmloegcmluin/sagitta ... lysis/data
Note ‘asciiUnicode.js’ and ‘levelEdas.js’.
https://github.com/cmloegcmluin/sagitta ... lysis/data
Note ‘asciiUnicode.js’ and ‘levelEdas.js’.
- Dave Keenan
- Site Admin
- Posts: 2180
- Joined: Tue Sep 01, 2015 2:59 pm
- Location: Brisbane, Queensland, Australia
- Contact:
Re: New [sub]...[/sub] and [sup]...[/sup] BBCodes
Excellent. And it's exciting to see that code!cmloegcmluin wrote: ↑Wed Jun 17, 2020 3:59 pm You’ll be happy to learn then, that I am already following these good practices in the code:
https://github.com/cmloegcmluin/sagitta ... lysis/data
Note ‘asciiUnicode.js’ and ‘levelEdas.js’.
I suppose you've seen the crazy Microsoft camel-case spec with its special case for 2-letter acronyms.
https://docs.microsoft.com/en-us/dotnet ... onventions
- cmloegcmluin
- Site Admin
- Posts: 1700
- Joined: Tue Feb 11, 2020 3:10 pm
- Location: San Francisco, California, USA
- Real Name: Douglas Blumeyer (he/him/his)
- Contact:
Re: New [sub]...[/sub] and [sup]...[/sup] BBCodes
Dave Keenan wrote: ↑Wed Jun 17, 2020 4:29 pm I suppose you've seen the crazy Microsoft camel-case spec with its special case for 2-letter acronyms.
https://docs.microsoft.com/en-us/dotnet ... onventions