𝕕𝕠𝕦𝕓𝕝𝕖-𝕀π•₯π•£π•¦π•”π•œ , π”‰π”―π”žπ”¨π”±π”²π”―, 𝖇𝖔𝖑𝖉-π–‹π–—π–†π–π–™π–šπ–—, 𝓫𝓸𝓡𝓭-𝓼𝓬𝓻𝓲𝓹𝓽 headings

Development
1

𝕕𝕠𝕦𝕓𝕝𝕖-𝕀π•₯π•£π•¦π•”π•œ , π”‰π”―π”žπ”¨π”±π”²π”―, 𝖇𝖔𝖑𝖉-π–‹π–—π–†π–π–™π–šπ–—, 𝓫𝓸𝓡𝓭-𝓼𝓬𝓻𝓲𝓹𝓽 and πš–πš˜πš—πš˜πšœπš™πšŠπšŒπšŽ Double-struck, Fraktur, bold-fraktur, bold script and monospace in plain text

are unicode math characters available without installing fonts. But they are only searchable as plain text when the plain text is hidden under <details> tags or a plugin spoiler block.
Has anyone tried integrating them properly?
They could be useful for headings but the plugin spoiler block can't be contained in a header and inline spoilers currently have no userstyle.css option to hide the body other than by a black block. eg. Stack overflow hidden text options
The <details> tag can be wrapped by <h > tags but are not recognised by the pdf preview or the outline plugin or the [TOC].
This is like using an image with title text as a heading

<h1>
  <a href="http://stackoverflow.com">
    <img src="logo.png" alt="Stack Overflow" />
  </a>
</h1>

Nowdays that would be title= which I want as plaintext next to the math unicode heading in markdown. I notice that inline ![ multimedia links have title text and can go in headers. The title text would still be indexed by search engines, heard by blind readers but not an in page search. This is an improvement over a comment that disapears after conversion from markdown. Its a kludge but it works and is searchable in the editor. The pdf preview does not jump to matches anyway so even though it does not find it, it is probably unimportant. Hopefully I can get a 1 pixel image inline but I doubt it. Local, so its not tracked or blocked. I will give an example in a reply when I find a 1 pixel image online that is not tracked. Not sure I can load those here.

The right way for search and replace.

The 2019 <math><mi mathvariant="math-fraktur">math font tags</mi></math> tags were designed partly with this common use in mind but they do not render in Joplin's pdf preview despite having the unicode available, (but do render in all browsers). Rendering this tag would allow writing in those fonts

  • easily
  • search-ably
  • with exported markdown converted to html headings
  • without needing a <details> tag.

It is not part of common mark so it would need to be added as a transcoding array (eg Dressup) that hid the original in a transparent microfont perhaps. That sounds like an addition to userstyle.css as well. I will ask the spoiler block developer about inline transparency instead.

As a side note. Although I doubt KaTex could go in a heading, it also uses direct unicode entry of these fonts (with a weird option to to install them seperately). It does include an option to set one of these math fonts as the default for KaTex blocks but this requires installing each of these fonts and and then listing them in the CSS which defeats my purpose.