BBCode Conversion Chart Status - CustodesTechnologia/System GitHub Wiki

Status and Chart of BBCode

This page documents the BBCodes that were used and their status after conversion. It also shows the HTML/CSS that was used to replace existing legacy BBCode idioms.

The Status

WNF = Will Not Fix

With respect to Notes, use this legend:

  1. Not enough content to warrant. Under 50 Posts. Fix Manually.
  2. Not enough content to warrant. Between 100 - 120 Posts. Fix Manually.

List

Fixed / Repaired

Due to the quantity of the legacy tags in the legacy data, these were fixed/reparied/managed.

BBCode Status Sections Updated HTML replacement Comment
b Done Forum Posts, Signatures <strong> DONE
caslonskullheader Fixed N/A N/A Built-In Editor Fix
clearfloat Done N/A N/A Replaced HTML in posts
i Done Forums, Signatures <em>
img Done Forums, Signatures <img class="ipsImage" ...>
size Done Forums, Signatures <span style="font-size:N;"> ... </span>
skullheader Done N/A N/A Built-In Editor Fix
skullheaderhalf Done N/A N/A Built-In Editor Fix
spoiler Done Forum <div class="ipsSpoiler" data-ipsspoiler=""><div class="ipsSpoiler_header"><span></span></div><div class="ipsSpoiler_contents">
u Done Forums, Signatures <span style="text-decoration:underline;">
url Done Forums, Signatures <a href=URL ...>
smallheaderhalf Done Forums TBD
topic Done Forums, Signatures <a href=URL ref=""> URL is derived from topic_id and title_seo

Will Not Fix

The numbers of posts with these legacy tags is too low to have impact or overcome the risk/time of changing the database.

BBCode Status Sections Updated HTML replacement Comment
acronym WNF N/A N/A See Note 1
argostest WNF TBD N/A See Note 1
article WNF TBD TBD See Note 1
background WNF N/A N/A See Note 1
basicheader WNF N/A N/A See Note 1
basicheaderhalf WNF N/A N/A See Note 1
button WNF N/A N/A See Note 1
captionleft WNF N/A N/A See Note 1
captionright WNF N/A N/A See Note 1
caslonheader WNF N/A N/A See Note 1
caslonheader2 WNF N/A N/A See Note 1
center WNF N/A <span ...> See Note 1
code WNF N/A N/A See Note 1
color WNF N/A N/A See Note 1
Defineobject WNF N/A N/A See Note 1
Definition WNF N/A N/A See Note 1
dropcap WNF N/A N/A See Note 1
email WNF N/A N/A See Note 1
font WNF N/A N/A See Note 1
hidden WNF N/A N/A See Note 1
hr WNF N/A N/A See Note 1
html WNF N/A N/A See Note 1
imageleft WNF N/A N/A See Note 1
imageright WNF N/A N/A See Note 1
indent WNF N/A N/A See Note 1
left WNF N/A N/A See Note 1
leftsidebar WNF N/A N/A See Note 1
lightboxclose WNF N/A N/A See Note 1
lightboxload WNF N/A N/A See Note 1
list WNF N/A N/A See Note 1
media WNF N/A N/A See Note 1
member WNF N/A N/A See Note 1
newcaptionleft Not Started N/A N/A See Note 1
openlightbox WNF N/A N/A See Note 1
php WNF N/A N/A See Note 1
post WNF N/A N/A See Note 1
quote WNF N/A N/A See Note 2
right WNF N/A N/A See Note 1
rightsidebar WNF N/A N/A See Note 1
sharedmedia WNF N/A N/A See Note 1
smallheader WNF N/A N/A See Note 1
smallspacemarine WNF N/A N/A See Note 1
smindent WNF N/A N/A See Note 1
snapback WNF N/A N/A See Note 1
spacemarine WNF N/A N/A See Note 1
sql WNF N/A N/A See Note 1
strike WNF N/A N/A See Note 1
sub WNF N/A N/A See Note 1
sup WNF N/A N/A See Note 1
table WNF N/A N/A See Note 1
td WNF N/A N/A See Note 1
th WNF N/A N/A See Note 1
tr WNF N/A N/A See Note 1
twitter WNF N/A N/A See Note 1
wfcaptionleft WNF N/A N/A See Note 1
wfcaptionright WNF N/A N/A See Note 1
wiki WNF N/A N/A See Note 1
xml WNF N/A N/A See Note 1

Details

Don't be alarmed. Many of these are simple to fix. The ones fixed already were good patterns to solve.

In general, any BBCode tag that is like this:

[tag] your stuff [/tag]

is simple. The parsing/grammar is easy.

In general, any BBCode tag that is like this:

[Foo=number] your stuff [/Foo]

is a bit more difficult because that number is either topic_id, post_id, etc.. and has to be correlated in the database. The way the software works, it wants the Friendly URL so the DB parsing has to look up the title_seo and then compose a URL based on the topic_id and the title_seo etc... This applies to [post], [article], [topic], etc... anything where the number is an ID to a thing in the Database.

In general, any BBCode tag that is like this:

[bar=RRGGBB] color me RRGGBB [/bar]]

or any other type where the argument is syntax sugar for the HTML, then it's easy to parse and reduce down to the HTML/CSS.

Another type that is like that but a bit more work because I have to reverse engineer the argument domains.

[font=font X] your stuff [/font]

The official names of fonts have to be used and so I have to check the font name in X against what the current new SW supports. Easy. Just a tedious job of verifying.

On to the Status:

⚠️ **GitHub.com Fallback** ⚠️