BB Code?

[Eric the Viking]

Tried to do strikethrough earlier, but couldn't. Is this a feature that's easy to turn on?

Personally I don't need a button or that sort of stuff - it's easier to type it straight in, but the correct BBcode doesn't presently work.

Optimistically,

E.

[AndyT]

Pretty sure it's not built in to the site. But when it's needed I just go to any online strikethrough text generator site you find, eg https://www.piliapp.com/cool-text/strikethrough-text/
Type ̶ ̶a̶n̶y̶ ̶o̶l̶d̶ ̶d̶r̶i̶v̶e̶l̶ words of finest wisdom, copy and paste.

[spb]

BBCode is definitely enabled in general, but phpBB's implementation of BBcode doesn't include strikethrough. At least in recent versions it's possible to enable it, but I can't imagine it's high up the priority list especially given that there are workarounds like the one Andy suggested.

[Eric the Viking]

I did have a look at Andy's link, but haven't time to fully check the output (I don't think I have a hex editor available presently - haven't used one since the eraly 1990s!). Not keen to use it unless I'm comfortable it's safe, but will check it out thoroughly when I have a moment. Dumping the output into SCITE (which might have a hex-display/edit function - not checked!), suggests it's using escaped characters, so that probably won't display properly everywhere..

BBCode, OTOH, is simply substituting characters in basic HTML, so ought to be totally "unexciting."

Hence my original request, although it's the first time in years I've tried to use it anywhere, and I'll admit it's hardly a must-have.

E.

[Dr.Al]

I did have a look at Andy's link, but haven't time to fully check the output (I don't think I have a hex editor available presently - haven't used one since the eraly 1990s!). Not keen to use it unless I'm comfortable it's safe, but will check it out thoroughly when I have a moment. Dumping the output into SCITE (which might have a hex-display/edit function - not checked!), suggests it's using escaped characters, so that probably won't display properly everywhere..

BBCode, OTOH, is simply substituting characters in basic HTML, so ought to be totally "unexciting."

Hence my original request, although it's the first time in years I've tried to use it anywhere, and I'll admit it's hardly a must-have.

E.

It seems to be using the original character and then two hex codes CC & B6. I'm not sure what codepage that is expecting (doesn't look like UTF8), but I wonder whether it's some sort of backspace character and then a horizontal line (i.e. write the letter, go back and then overwrite a line). That's all a complete guess of course.

[AndyT]

All I can say is that it works, and I am really happy that my computer now automatically copies all my secret information to a special secure storage site for the low low fee of only $500 a month!

[spb]

It seems to be using the original character and then two hex codes CC & B6. I'm not sure what codepage that is expecting (doesn't look like UTF8), but I wonder whether it's some sort of backspace character and then a horizontal line (i.e. write the letter, go back and then overwrite a line). That's all a complete guess of course.

It is UTF-8, actually - CC B6 is the UTF-8 encoding of U+0336, COMBINING LONG STROKE OVERLAY, which is defined as overlaying on top of the previous character. The generated text will work anywhere that understands UTF-8, which includes any web browser released in the last 20 years.

Some terminal emulators still have problems with combining codepoints messing up their character counting, but that shouldn't stop you using it on the web.

[Dr.Al]

It seems to be using the original character and then two hex codes CC & B6. I'm not sure what codepage that is expecting (doesn't look like UTF8), but I wonder whether it's some sort of backspace character and then a horizontal line (i.e. write the letter, go back and then overwrite a line). That's all a complete guess of course.

It is UTF-8, actually - CC B6 is the UTF-8 encoding of U+0336, COMBINING LONG STROKE OVERLAY, which is defined as overlaying on top of the previous character. The generated text will work anywhere that understands UTF-8, which includes any web browser released in the last 20 years.

Some terminal emulators still have problems with combining codepoints messing up their character counting, but that shouldn't stop you using it on the web.

That makes sense, thanks. I've found that some UTF-8 characters don't work on this website - nothing to do with the browser, I think it's just the process of writing the text into the backend database (or whatever) fails as it hasn't been designed to work with UTF-8 properly - it produces a lovely cryptic error message too! I guess the U+0336 thing is okay in this case.