FA+
Shop
Verification sheet for the BBCode parser replacement
13 years ago
This journal is a test for the new BBCode parser I am working on. It is not ready yet.
The codes for the current parser of FA can be found on my previous journal: http://www.furaffinity.net/journal/441426/
The parser is based off pecl_bbcode PHP extension. The goal is to write a proper replacement to the current BBCode and URL parser, which currently is just a collection of regular expressions that process the text before displaying it.
To those viewing this journal on FA it would likely appear to be horribly broken. The actual replacement parser is being implemented on a closed sandbox; that's where the page would look normal.
Initially only the subset of BBCode tags that already exist on FA are going to be (re)implemented, but you are welcomed to new tags in the comments; things like [code][list][/code]s and [code][video][/code] and so on.
[code]bold text[/code]: bold text
[code]italic text[/code]: italic text
[code]underlined text[/code]: underlined text
[code]striked out text[/code]: striked out text
[code]Text supscripted[/code]: Text supscripted
[code]Text subscripted[sub][/code]: Text [sub]subscripted
[code]red text[/code]: red text
[code]
[code]
[code]
[code]
[code][size=1]size 1 text[/size][/code]: [size=1]size 1 text[/size]
[code][size=2]size 2 text[/size][/code]: [size=2]size 2 text[/size]
[code][size=3]size 3 text[/size][/code]: [size=3]size 3 text[/size]
[code][size=4]size 4 text[/size][/code]: [size=4]size 4 text[/size]
[code][size=5]size 5 text[/size][/code]: [size=5]size 5 text[/size]
[code]
[list=1]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=1]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=01]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=01]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=a]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=a]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=A]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=A]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=i]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=i]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=I]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=I]
[*]list item 1
[*]list item 2
[/list]
[code][progress=75]description[/progress][/code]: [progress=75]description[/progress]
[code][hr][/code]: [hr]
[code][divider][/code]: [divider]
[code]'Sup™[/code]: 'Sup™
[code]Spam®[/code]: Spam®
[code]single line, un-named quote[/code]: single line, un-named quote
[code]multi line,
un-named quote[/code]: multi line,
un-named quote
[code]yak wrote:single line, named quote[/code]: yak wrote:single line, un-named quote
[code]yak wrote:multi line,
named quote[/code]: yak wrote:multi line,
named quote
[code]yak wrote:multi line, named quote with bbcode content:
[code]bold text[/code]: bold text
[code]italic text[/code]: italic text
[code]underlined text[/code]: underlined text
[code]striked out text[/code]: striked out text[/code]: yak wrote:multi line, named quote with bbcode content:
[code]bold text[/code]: bold text
[code]italic text[/code]: italic text
[code]underlined text[/code]: underlined text
[code]striked out text[/code]: striked out text
[code]this is [quote]an example ofa series of [quote]nested quotes[/quote][/quote][/code]: this is [quote]an example ofa series of [quote]nested quotes[/quote][/quote]
[code]http://www.furaffinity.net[/code]: http://www.furaffinity.net
[code]www.furaffinity.net[/code]: www.furaffinity.net
[code]https://www.furaffinity.net/trac/tr.....cket/1[/code]: https://www.furaffinity.net/trac/trunk/ticket/1
[code]http://furaffinity.net?a=b&c=d[/code]: http://furaffinity.net?a=b&c=d
[code]some@email.com[/code]: some[at]email.com
[code]yak's page[/code]: yak's page
[code]yak's page as a relative URL[/code]: yak's page as a relative URL
[code][video]http://www.youtube.com/watch?v=p8t4.....video][/code]: [video]http://www.youtube.com/watch?v=p8t41avFuCc[/video]
[code][video]http://vimeo.com/8623092[/video][/code]: [video]http://vimeo.com/8623092[/video]
[code]
yak[/code]: yak
[code][/code]:
[code]yak[/code]: yak
[code]<<< PREV | FIRST | NEXT >>>[/code]: <<< PREV | FIRST | NEXT >>>
The codes for the current parser of FA can be found on my previous journal: http://www.furaffinity.net/journal/441426/
BBCode verification sheet
This journal is going to be used as a verification sheet for a replacement BBCode parser currently in development.The parser is based off pecl_bbcode PHP extension. The goal is to write a proper replacement to the current BBCode and URL parser, which currently is just a collection of regular expressions that process the text before displaying it.
To those viewing this journal on FA it would likely appear to be horribly broken. The actual replacement parser is being implemented on a closed sandbox; that's where the page would look normal.
Initially only the subset of BBCode tags that already exist on FA are going to be (re)implemented, but you are welcomed to new tags in the comments; things like [code][list][/code]s and [code][video][/code] and so on.
Basic formatting
[code]bold text[/code]: bold text
[code]italic text[/code]: italic text
[code]underlined text[/code]: underlined text
[code]
[code]Text supscripted[/code]: Text supscripted
[code]Text subscripted[sub][/code]: Text [sub]subscripted
[code]red text[/code]: red text
[code]
Left aligned text[/code]: Left aligned text[code]
Centered text[/code]: Centered text[code]
Right aligned text [/code]: Right aligned textText sizing
[code]
H1 headline
[/code]:H1 headline
[code]H2 headline
[/code]:H2 headline
[code]H3 headline
[/code]:H3 headline
[code]H4 headline
[/code]:H4 headline
[code]H5 headline
[/code]:H5 headline
[code][size=1]size 1 text[/size][/code]: [size=1]size 1 text[/size]
[code][size=2]size 2 text[/size][/code]: [size=2]size 2 text[/size]
[code][size=3]size 3 text[/size][/code]: [size=3]size 3 text[/size]
[code][size=4]size 4 text[/size][/code]: [size=4]size 4 text[/size]
[code][size=5]size 5 text[/size][/code]: [size=5]size 5 text[/size]
Lists
[code]
[list=1]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=1]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=01]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=01]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=a]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=a]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=A]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=A]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=i]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=i]
[*]list item 1
[*]list item 2
[/list]
[code]
[list=I]
[*]list item 1
[*]list item 2
[/list]
[/code]:
[list=I]
[*]list item 1
[*]list item 2
[/list]
[code][progress=75]description[/progress][/code]: [progress=75]description[/progress]
[code][hr][/code]: [hr]
[code][divider][/code]: [divider]
Smilies
[code]All your base are belong to us©[/code]: All your base are belong to us©[code]'Sup™[/code]: 'Sup™
[code]Spam®[/code]: Spam®
Quotations
[code]single line, un-named quote[/code]: single line, un-named quote
[code]multi line,
un-named quote[/code]: multi line,
un-named quote
[code]yak wrote:single line, named quote[/code]: yak wrote:single line, un-named quote
[code]yak wrote:multi line,
named quote[/code]: yak wrote:multi line,
named quote
[code]yak wrote:multi line, named quote with bbcode content:
[code]bold text[/code]: bold text
[code]italic text[/code]: italic text
[code]underlined text[/code]: underlined text
[code]
[code]bold text[/code]: bold text
[code]italic text[/code]: italic text
[code]underlined text[/code]: underlined text
[code]
[code]this is [quote]an example ofa series of [quote]nested quotes[/quote][/quote][/code]: this is [quote]an example ofa series of [quote]nested quotes[/quote][/quote]
URLs and links
[code]http://www.furaffinity.net[/code]: http://www.furaffinity.net
[code]www.furaffinity.net[/code]: www.furaffinity.net
[code]https://www.furaffinity.net/trac/tr.....cket/1[/code]: https://www.furaffinity.net/trac/trunk/ticket/1
[code]http://furaffinity.net?a=b&c=d[/code]: http://furaffinity.net?a=b&c=d
[code]some@email.com[/code]: some[at]email.com
[code]yak's page[/code]: yak's page
[code]yak's page as a relative URL[/code]: yak's page as a relative URL
Embeddable videos
[code][video]http://www.youtube.com/watch?v=p8t4.....video][/code]: [video]http://www.youtube.com/watch?v=p8t41avFuCc[/video]
[code][video]http://vimeo.com/8623092[/video][/code]: [video]http://vimeo.com/8623092[/video]
Site-specific features
[code]
yak[/code]: yak[code]
[/code]: [code]yak[/code]: yak
[code]<<< PREV | FIRST | NEXT >>>[/code]: <<< PREV | FIRST | NEXT >>>
Can you link to an example?
I'm just trying to see if when I make something bold it makes the text go subscript. (Test #1)
I'm just trying to see if when I make something bold it makes the text go subscript. Trying to see what makes this happen if maybe it's a dual line thing. (Test #2)
I'm just trying to see if when I make something bold it makes the text go subscript. Trying to see what makes this happen if maybe it's a dual line thing with smiley face. (Test #3)
...gonna see if these do it. If not, I'll search my messages and see if I can find an example.
Another test you may want to add to this page would be more than 5 consecutive autolinks. The existing parser will break every 5th link by adding a space that shouldn't be there, and I think it has to do with a forced line break every 200 characters to prevent long single lines. If I encase each link with the url tag and give it a title, all the links will work fine. Only autolinks have this problem.
http://www.furaffinity.net/view/6693019/
http://www.furaffinity.net/view/6693019/
http://www.furaffinity.net/view/6693019/
http://www.furaffinity.net/view/6693019/
http://www.furaffinity.net/view/6693019/ <- (should be broken)
http://www.furaffinity.net/view/6693019/
[-, -, -]
You substitute the dashes for the numbers of your submissions.
The first dash represents "PREV," the second dash represents "FIRST," and the third dash represents "NEXT."
Suppose you had 10 submissions that you wanted to use this tag on, and there numbers were as follows:
1
2
3
4
5
6
7
8
9
10
...and you wanted to put submission number "1" as the FIRST in the series, leading up to submission number 10? Your codes would look like this:
Submission #1
[-, -, 2]
Submission #2
[1, 1, 3]
Submission #3
[2, 1, 4]
Submission #4
[3, 1, 5]
Submission #5
[4, 1, 6]
Submission #6
[5, 1, 7]
Submission #7
[6, 1, 8]
Submission #8
[7, 1, 9]
Submission #9
[8, 1, 10]
Submission #10
[9, 1, -]
Now every submission is in order, where submission #1's tag doesn't have a number for its "PREV" and "FIRST" slots because it's the first submission, and nothing else came BEFORE it. And submission #2 leads "BACK" ("PREV") to #1, has its "FIRST" submission link set to go back to #1, and has its "NEXT" submission link set to go to #3. And #3 goes "BACK" to #2, has #1 as its "FIRST," and goes "NEXT" to #4, etc...
It seems simple here, but when you actually do it you have to take note of the numbers of your submissions. Like if your FIRST submission number was, let's say, "1000000" (one-million), your second was "1100000" (one-million one-hundred thousand), your third one was "1200000" (one-million two-hundred thousand), and your fourth one was "1300000" (one-million three-hundred thousand)? If number "1000000" was the FIRST submission, and number "1100000" was the SECOND submission, and number "1200000" was the THIRD submission, and number "1300000" was the FOURTH submission, the tags for the first three submissions should look like this:
Submission #1 (1000000)
[-, -, 1100000]
Submission #2 (1100000)
[1000000, 1000000, 1200000]
Submission #3 (1200000)
[1100000, 1000000, 1300000]
It might seem complicated, but it's actually just a matter of knowing WHICH submissions you want in WHAT order.
Also, the "submission number" is the number you see in the link for your submission. Example:
http:// www. furaffinity.net /view/[the submission number]/ (I put spaces in the link so it wouldn't go to anyone's random submission... >.>).
The number just after the word "view" (or the word "full") in your submission links is the submission number. Once you gather those numbers together and decide what ORDER you want them to come in, you go from there.
Sorry for the long comment, but it's hard to explain in just a few words alone. x.x
TEST[rt]TEST[/rt]
:phoenixaudubon:
TEST
It's more advanced, probably faster, and allows for more stuff to be added, easier.
So yeah, the current parser doesn't like the new markup very well :)
Does the new parser support quotes inside quotes?
There was another idea of this however, that'd make reading notes with lots of replies in a different way. Sort of like google mail. Each reply minimized in it's own box above the new one. Then again that'd probably be harder to do.
Notes: notes are not logically connected to one another and there is no way to know whether any given note is a reply to another note, or has replies of its own. Otherwise what you suggest would have been implemented already. Notes system needs, and will be rewritten when time permits.
I tend to come up with a lot of ideas for every place I enjoy staying at, but I'm never heard so I stopped giving them. :P Example, EVE Online has a suggestion board. I've had many great ideas that only helped absolutely everyone, even the staff. And they were ignored even though it would take but like 10 minutes to an hour at most of coding with the amount of people they have working on the game. Every idea over the past 3 years has been ignored as if I don't exist. I lost my faith in giving input to anything anymore. :P
Yea, sometimes something seems simple but isn't. I didn't say anything on this site was simple, I just pointed out how even simple ideas got ignored and it made me not wish to give input anymore. But anyhow. I'll let you get back to whatever it is you tend to do. :P
http://help.furaffinity.net/article.....and-Codes.html
Looks much nicer, don't you agree? :P With the [code] thing not working here, it's kind of a moot journal since no one can see the actual code to see how to do it.
2
1
I tried the code thing and it didn't work.
Centered Text[ center]Centered Text[/center] (Remove the space)
I found one "small" annoyance with the existing parser that "shouldn't" be too hard to fix. (I know, things aren't always as simple as they seem, but this one should be.)
When we use : iconusername:, or : usernameicon:, the icons are not properly vertically centered with any text on the same line. The icons appear too low, in relation to the text. This misalignment can be exaggerated greatly if a user needs to use a browser font that is larger than the default - perhaps because of low vision.
It appears that the code you currently use,
* <img src="//a.facdn.net/username.gif" title="username" alt="username" align="middle">
is not behaving accurately as intended, and the relative text alignment with the icons changes depending on how large or small the user makes their browser font.
However, this code,
* <img style="vertical-align:middle;" src="//a.facdn.net/username.gif" title="username" alt="username">
works perfectly. It vertically center aligns properly, no matter how large or small the user makes their browser font, making the result look much better.
It appears that align="middle" is somewhat broken, but that style="vertical-align:middle;" works perfectly. Just something to consider, the next time you go into the code. It's subtle, but it will make things look a little better.
Another thing that would be nice is if the left, center and right justify codes didn't force a new line. I'd love to be able to do something likes this :
[ left]column one[/left] [ center]column two[/center] [ right]column three[/right]
[ left]- - - - - - - -[/left] [ center]- - - - - - - -[/center] [ right]- - - - - - - -[/right]
[ left]aaaaaaa[/left] [ center]should be centered[/center] [ right]xxxx[/right]
[ left]bbbbb[/left] [ center]kkk kkk kkkk[/center] [ right]should be right justified[/right]
[ left]should be left justified[/left] [ center]lllll[/center] [ right]zz[/right]
Currently, this will display as 15 lines, instead of as 5 lines as intended. It's currently inserting a new line after each [/left], [/center] or [/right]. Is there any easy way to prevent that?
Can you allow to work. There are times when spacing things would be nice, and there is no easy way to do that, since HTML normally eats additional spaces. Perhaps a [nbsp] code can be added.
Feel free to hit me if I'm annoying you with ideas.
"smilie smile"
There is a syntax called: [noparse]Bold Text[/noparse] ⇒ [b]Bold Text[b] (I removed the / at the end of the syntax).
It would make your life easier in these formatting journals.
the [noparse] [/noparse] literally forces the system to fail to parse the formatting inside of the [noparse] [/noparse].
Or shows the syntaxes. (tag).
BBCode Tester
aaaa