Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 ... 5 6 [7]

Author Topic: This Forum's BBCode Help Thread  (Read 12224 times)

KittyTac

  • Bay Watcher
  • Impending Catsplosion. [PREFSTRING:aloofness]
    • View Profile
Re: This Forum's BBCode Help Thread
« Reply #90 on: September 20, 2018, 01:14:33 am »

Yandex (which is based on Chromium) shows WIngdings.
Logged
Don't trust this toaster that much, it could be a villain in disguise.
Mostly phone-posting, sorry for any typos or autocorrect hijinks.

roseheart

  • Bay Watcher
  • Ubersecretary Supreme
    • View Profile
Re: This Forum's BBCode Help Thread
« Reply #91 on: January 22, 2019, 05:53:37 pm »

1.
^LAST

2.
LAST
(right-click copy of quote address)

3.
LAST
(direct copy of post url, actually the same url as last one, so redundant)

4.
LAST
(browser bar url when clicking on post title url, also the same/redundant)

Edit 1: Only the first allows the link to open in the same window, on PC. Windows Chrome.

Edit 2: Same result on Android Chrome (phone).

Example Use:


Code: [Select]
[center][table]
[tr][td]FirstQuoteHere[/td][td]LastQuoteHere[/td][td]NextQuoteHere[/td][td]SkipQuoteHere[/td][/tr][/table][/center]

Code: [Select]
[center][size=12pt]◀◀[/size][/center]
Code: [Select]
[center][size=12pt]◀[/size][/center]
Code: [Select]
[center][size=12pt]▶[/size][/center]
Code: [Select]
[center][size=12pt]▶▶[/size][/center]
Just forward and back:

Code: [Select]
[center][table]
[tr][td]LastQuoteHere[/td][td]NextQuoteHere[/td][/tr][/table][/center]

« Last Edit: January 22, 2019, 08:25:28 pm by roseheart »
Logged
The grass is not greener on the other side, itís greener where you water it.

Patreon

Starver

  • Bay Watcher
    • View Profile
Re: This Forum's BBCode Help Thread
« Reply #92 on: February 02, 2021, 11:05:08 pm »

As I've been wrestling with an annoying niggle, I thought I'd post my various findings here, in case they're useful.

Note that several things have changed since my last (2018) post, not far above this one, including which mobile device (and browers upon it) I'm using. And that I am satisfied that all my various issues (like the continuing [abbr] incomplete functionality) are at my end.

Basically, the [font]-tag is entirely dependant upon the reader's system taking the paramaterised 'suggested' font that is supplied (via simple HTML) as the font-family style parameter to a <SPAN>. As with the Wingdings, above, it works when it can work. Other tags, when translated, specify (directly and/or via CSS) a fuller font-family, particular ones that are specifically fixed-width users. Again, it depends upon the end-user's system, but it at least includes multiple fallbacks.

Test .W_- font=courier - fails to become Courier-like on this browser+device, after invoking any font-family style for the sole parameter (browser/device issue)
(Note that I haven't discovered any cascaded use for the bbc_font class that this could invoke, but it wouldn't help this issue much anyway, the way it 'works'.)

Test .W_- font=courier new - fails on this browser (could it work with quotes passed around to multiword style?)

[font="courier new"]Test .W_- font="courier new"[/font] - entirely fails to parse as BBCode (doesn't appear to like me giving it quotes to transform into the HTML form)

Test .W_- font=monospace - works on my device, though it's a sub-sized font in direct comparison with non-monospace of same pointsize spec. Unknown if "monospace" is universally acceptable, though I think it'll have a decent chance to widely so.

Code: [Select]
Test .W_- code-tagged - invokes DIV-nested style that specifies a thorough font-family listing that works, even if just upon the one last listed (monospace). But doesn't help with SPAN-type inline styling.

Test .W_- tt-tagged - 'normal' fixed-width (calls bbc_tt style in CSS; full family list with monospace but renders larger than font=monospace, so may be one of the other after all). I shall probably use this option more in future, though it isn't rendered via any 'editor' button so is slightly fiddlier.

You, dear reader, may have entirely a different set of results for everything I describe in this post. Which is more a vanity project for myself than an instruction-manual.



And, while I'm here, I'll echo another recent conversation I had (with a fellow member of this parish) about the Glow and Shadow tags.  They render badly here (i.e. this particular device, 2020-vintage rather than possibly half a dozen years older). Pinch-zooming indicates that they are placing correctly (Glow and Shadow layer sit behind, and slightly offset to, the primary version of the text) and the zoomed-in or font-upscaled effects are pleasant and readable (though may need side-scrolling!), but at 'normal' size the glow overdominates. A purple 'glow' behind a fuschiaedit: no, orchid I meant text just looks blurry purple (but then fuschiaedit: orchid! and purple are a similar hue). Changing to a 'red' glow for some notable contrast, the glow clearly dominates (it actually gives a rose-pink effect, but still looks just blurry). Giving a totally contrasting glow (e.g. green) makes it messy and blurry at non-zoomed appearance.

Obviously, again, somewhat specific to my device (and eyes), but FYI while this is all at the forefront of my mind.  i.e. full standardisation/uniformity of presentation is a dodgy assumption to make, even these days. But I hope this helps someone else in some unknown future who goes looking for similar reasons for similar issues.
« Last Edit: February 03, 2021, 01:03:11 am by Starver »
Logged

roseheart

  • Bay Watcher
  • Ubersecretary Supreme
    • View Profile
Re: This Forum's BBCode Help Thread
« Reply #93 on: February 03, 2021, 12:48:13 am »

^Nice bump. I should really remake this thread on my new account, so I can compile all the additions in the OP. This will be that if it happens. I have a lot of little projects like this one.
Logged
The grass is not greener on the other side, itís greener where you water it.

Patreon
Pages: 1 ... 5 6 [7]