Malformed output when using bottom command with inline automatic encoder

[kotx]

.bottom test produces 💖💖✨🥺,💖💖,💖💖✨🥺💖💖✨🥺,
but using https://bottom-software-foundation.github.io/bottom-web/ to decode, the input is said to be malformed. Using https://bottom-software-foundation.github.io/bottom-web/ to encode test produces 💖💖✨🥺,👉👈💖💖,👉👈💖💖✨🥺👉👈💖💖✨🥺,👉👈
which is different.

[romdotdog]

The byte separators (👉👈) are gone. In my time using this plugin, (I now use my fork) I haven't encountered this issue. Is it any multi-byte text that you encounter this issue with?

aaa should yield 💖✨✨✨✨🥺,,👉👈💖✨✨✨✨🥺,,👉👈💖✨✨✨✨🥺,,👉👈
... should yield ✨✨✨✨🥺,👉👈✨✨✨✨🥺,👉👈✨✨✨✨🥺,👉👈

[kotx]

@romdotdog Seems to be because the default inline bottom prefixes and suffixes collide with the byte separators. It works after replacing them/disabling automatic encoding.
https://github.com/bottom-software-foundation/power-bottom/blob/need_top/components/Settings.jsx#L65
This seems to be the case on your fork as well. I'd be glad to open a PR, but I'm not sure what to put as the default prefix/suffix.

[romdotdog]

I'll pull from upstream whatever happens :-)
How about tilde (~)?
I'd also like to hear @SebbyLaw's thoughts

[kotx]

I'll pull from upstream whatever happens :-)
How about tilde (~)?
I'd also like to hear @SebbyLaw's thoughts

Tildes (~~) are used in markdown for strikethrough, though.