Hello,

There is no doubt about it: "web is bloated".

Everyone, all, talk that the web browsers take a vast amount of resource and memory. Internet browsers make computers run slow. There is an important increase of CPU cycles. Many people complain that their browser is slow, so, they need to buy a newer PC. New Windows, but the system takes more more Endless story, right? Users most often need to read news, simple documents, and maybe POST few things. These many operations are most often simple. For simple Markup document, simple format, you may make use of your simple low resource/hardware perfs Kindle ebook for instance. HTML5? -Too heavy. Mobile html? Or, original 18-20 functions of HTML 1-2 ? Asciidoc? (forget Markdown due to ---- ==== much too complex to programme). Actually ASCIIDOC has a much better Markup syntax, since it is less complex than HTML and with few fopen/fgets/... string analysis, a document can be rendered. Wanna read your news on your Ebook Kindle, mobile, Raspberry without important resource dependency? Your Kindle is pretty slow, right? Shall it be slow? - No, since Markup is just few lines of C code to render a markup document. Instead of keep using Firefox, could you benefit of programming a graphical universal markup non-bloated browser (HTML?)? Dillo is a good idea, but it won't be compiled on a Kindle?

Sorry for the very very bad grammar of the prev paragraph. Don't bash, this thread is for positive mind and for plain C programmers only.

You are gently, kindle'ly, invited you to discuss within this thread on small resource markup syntax, markup document renderers, and portable plain C compiling/programming.

Hello,

I prefer ASCIIDOC to anything else since it is easy to convert using plain C language to html. Sections of ASCIIDOC are easy to handle with C (one on the line with '=' char(s)). Very probably someone is directly uploading Asciidoc page and lets do PHP the magic to render (simply convert) it directly on the website. I can convert my C source code to php, if you'd like. Let me know.

Maybe, would you likely know an already existing PHP code to render ASCIIDOC on website?

In 1983 I worked with ZOG which was a hypertext system that was used for interactive documents made up of formatted text, pictures and links. It ran fine on a 6 MIPS computer without any of the bloat and frills taken for granted today.

95% of websites run fine with Javascript disabled. It is a feature I play a lot in the reasonably old Opera 11 and 12 versions (the last versions before Opera changed to Chromium code base and I stopped using its current version). These versions (11 and 12) are reasonably light in RAM, and fairly compatible with most websites I use (although I force the use of mobile versions of Twitter and Facebook, which are, IMO and needs, better).

If I would build a website for anything with mostly text and images, I would use HTML 3.2. HTML 4.01 with a few simple CSS styles are also practical and light resource needs (and compatible with many many many different platforms and browsers, old and new). HTML5, like you said... "thank you, I pass it".

"links" is a textmode browser I eventually use. Its compatibility with some websites is surprising (in a very good way) to me! (:

Salut,

I don't understand the need for a PHP code on the server side as the asciidoc application's purpose is to convert a text file in Asciidoc format to a static (x)html page, that will be rendered as any the web page by the browser.

As an example this page:
http://slint.fr/old/fr/tools.html
was built from the file "tools.fr.txt" with this simple command:
where CONF_FILE is the config file for asciidoc, ll=fr for French and page=tools
You can see the source file tools.fr.txt clicking on "Texte source" on the bottom of the menu on the left of the web page.

PS See also the link to convtags in my signature.

PPS Did you rewrote the Python application asciidoc.py in C? Is your version complete then?
I guess you did that as an exercise, as the python app is fast enough (a few seconds to build the whole website whose root is http://slint.fr/old/ here). Or you could use asciidoctor if you prefer Ruby.

this is really amazing.
http://slint.fr/old/tools.fr.txt

I would think to upload via ftp the Asciidoc only documents (txt) on my website. And I can do even edit it with my phone or anything. No need of conversion at all, since Php does the rest to make the html. What ddo you think about this idea?

ZOG is no longer much documented. In 1983, computer were running on nothing (few bytes)

Nothing good:

1. You will need to write a program in PHP , somehow reinventing the wheel as it will do the same things as asciidoc.py (in python) or asciidoctor (in Ruby). It will take you months to provide the same features (if you don't give up), for no benefit that I can think of. Do I miss something?
   Also your statement "no conversion at all" is wrong as the conversion would be done by the PHP script, but it would still be a conversion.
2. If you goal is to build the html files on the fly from the txt files it would be way easier and faster to execute a command similar to the one in my last post as a CGI script on your web server. But what for? I don't see any advantage over providing already converted html pages.

Tiny PHP code to render ASCIIDOC on your website?
Programming a graphical universal markup non-bloated browser (HTML?)

Although not duplicates, these two threads by the same OP share the theme of tiny vs bloat, and ASCIIDOC rendering on the web.

Neither asks a programming question but seem intended to promote a general discussion of their subject. As such, they have been combined and moved from the Programming forum to the General forum where they will have better exposure for that purpose.

In few hours, it is easy to make run a PHP code that does several syntax functions of ASCIIDOC.
I still wonder why you wouldn't find it comfortable to make a website directly without cumbersome converting. PHP does the job and it can save you a bunch of time.

But the best would be a tiny browser that understand asciidoc, which is easy in C language.

These statements make me think that you have no idea how much work is needed to to do what you suggest, assuming that you really know what you are talking about, of which I am not sure.

I doubt that you be able to write a small program in C or PHP implementing a significant subset of ASCIIDOC's syntax. Take it as a challenge

WIKI:
It is not complicated to convert basic syntax (**only basics**) of asciidoc using PHP to html. Tu sais probablement aussi le faire, Didier... herewith what can do PHP asciidoc to html on the site. Let me know if you need something like this, or directly you can give me syntax input and html output so that I code it. I can do it.

It shall look after conversion: https://pastebin.com/raw/W4tCvnHe
Here I used libreoffice to make it to html.
Afterwards, I clean up a bit the html code, and I introduce functions into the PHP code. It is fairly possible. I see no difficulty at all. Actually, when you look well, isn't HTML very ugly? ASCIIDOC has a nicer look and is much nicer for eyes. Wanna continue with html5,6,7...10? I am curious about the real meaning since programmers will become dependent to their system due to lack of clarity of HTML source code. Definitely basic ASCIIDOC (or other minimalist markup's) should be first available on a browser.

I don't need that, as I already stated.
This is what I used as specification to write convtags. See also this article I wrote to know most syntactic constructs. If you can read Python, you can also directly look how Stuart Rackham did it in asciidoc.py, attached as asciidoc.py.txtI will believe you when will have done it.

Attached Files

asciidoc.py.txt (248.2 KB, 703 views)

For headers (section), bold,... items, and tables, might be a first step, leet's say.
= gives html title
== gives html header h1
=== gives html header h2
...
right?
I found the syntax : http://powerman.name/doc/asciidoc#_document_header

Asciidoc or maybe there might be better choice? markdoc? bbcode?

You would have find that in the documents I linked to, had you read it. And that just 1% of the syntax or so...As long as your aim is just to feed a discussion but you not do not intend to do anything beyond that (like coding something), every markup is fine