BBcode Web

I have to admit I am not the BBcode EXPERT like some of you here, but I propose the following:

What about a collaborative project to implement an alternative to webpages on the basis of BBcode?
It could run on http or be similar to Gopher or Usenet, just more practical for our proposes.... The first task will be to establish a consensus on the file(transfer)protocol.

I suggest using C99 for implementation.

Possibly we can come up with something that might be widely used in the future.
Who is in?

I don't quite understand what you want. To write pages in BBCode and then have a distinct client program to render it? Why?

>>2
I mean what's the difference between BBCode and HTML really? The different flavor of braces? Make it in Sexps if you are at it.

Something based on TeX or S-Expressions would be better than BBCode IMO.

>>2
Why?
Well, HTML is shit and the W3C is going to keep using the same terrible XML base for all future versions.

I propose to write a complete ^Se_xpCode _t^{o B}_BCode Compiler for Shii_tchan, instead.

(encoding utf-8)
(css "lmltest.css")
(title Sample Light Markup Language document)
(emphasis Text) outside of parantheses is printed as is. Left parentheses are written using the (#code (lp)rp(rp)) escape sequence and right ones are written using the (#code (lp)lp(rp)) escape sequence.
As with (image "texlogo.png" TeX), newline characters delimit paragraphs. You can use (lp)br(rp) to go to the next line in a paragraph.
(#buio ONE WORD: THE FORCED INDENTATION OF CODE!!)(br)Thread over.
The following CSS was used for this document:
(#code (load-text "lmltest.css"))
The # prefix denotes a custom element that doesn't have semantic significance, as with HTML's span and div elements. The load-text form that causes the browser to fetch the file and insert it. I chose to keep CSS because it's actually pretty good.
What do you think? It's only a draft of course, but I think it's already way better than HTML. We could eventually add a scripting language that would use Lisp's list manipulation functions instead of the retarded DOM API.

>>6
I prefer SXML/Xexprs.
Also, S-expressions do not preserve whitespaces.

>>7
When did I say those were S-expressions? It's more like a TeX with Lisp-like syntax, really.

>>6
Yes that would work too, and would probably have more functionality than bbcode will ever have.

But besides that: There is no agreement on how to use lisp expressions that we can build upon
And most importantly: BBcode is more widespread in any matter almost anybody on the internets knows about it.

Whats the benefit of the most efficient markup language when only a elite group of people already knows it? Content will be  higher quality but to sparse by any standards, do you want that?

there's no
spoiler:
    reason
for it to not use
bold:
    italic:
        underline:
            overline:
                pythonic
syntax
italic:
    !

We should replace BBCode with something that just uses CAPITAL LETTERS to denote content type.



BEGIN:PARAGRAPH>{({
  BEGIN:ESCAPE>{({H})}<ESCAPE:ENDello
  BEGIN:ESCAPE>{({W})}<ESCAPE:ENDorld
})}<PARAGRAPH:END

Sample "Hello World" document.

>>7
Xexprs
Herpes

>>12
I'm sorry.

^BO^NERLA_NG ⁱs b^e_tter t_han _BBC_ode

>>14
No, it's not. Stop for^cing bon_erlang.

since no suggestion on the original topic was made...

how about that: Use http and mime types to communicate the markup language to the client. Everyone is responsible for his own syntax ITT.

inb4 a implementation in something other than C

>>16
how about that: Use http and mime types to communicate the markup language to the client.
There's a better way. The client should put text/bbcode in the Accept field of the request, and then the server can choose to give him HTML or BBCode while still preserving backwards compatibility.