Left aligned paragraph.

Right aligned paragraph.

Centered paragraph.

This is a very long, almost never ending, sentence with the sole purpose to demonstrate how a justified paragraph would look like if the sentence wraps around several lines. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

/* Hello  */

#include <stdio.h>

int main(void)
{
printf("Hello World\n");
}

/* Hello  */

#include

int main(void)
{
printf(“Hello World\n”);
}

Tries this

###. Comment blocks are not supported.

Heading

heading 2

heading 3

heading 4

heading 5

heading 6

Shout.

On the right?

In the middle?

This paragraph is fully justified. Oh yes it is. This paragraph is fully justified. Oh yes it is. This paragraph is fully justified. Oh yes it is. This paragraph is fully justified. Oh yes it is.

Can headings be fully justified is the question we ask ourselves today. Maybe they can? Can headings be fully justified is the question we ask ourselves today. Maybe they can? Can headings be fully justified is the question we ask ourselves today.

Strong versus Bold. Emphasis versus Italic versus citation. strikethrough, inserted, ^superduper, _submariners, span, code.

What does double-equals do? Nothing at all.

Definition lists?

Yes
Further lines
of definition.

Indented a bit.

Indented some more.

Three indentings.

All the indents.

גשם חזק מאוד

^ That should be over there >

Citation quotes are unsupported

Footer is unsupported

Multiline comments unsupported

• List
  • Ooh
    • Triple
    • ooh
  • Ah
• Lost

1. Lust
   1. Ghee
      1. Clarified
   2. Butter
2. Last

Footnote¹
Unreferenced footnotes not supported[1!]

Named footnotes unsupported[#shame]

TLDR

Oh, you can use colours.

And now the footnotes

¹ Footnotes always have back-link

note#shame. Tut.

notelist.

Header 1

Header 2

Header 3

Header 4

###. This is a textile comment block.
It will be removed from your document.
Or not, might be a versions thing!

1. help
   1. help
      1. help

html comments work

I believe that most code recipes can be improved using ghee. Or haddock. [Edit, with respect to Rick: Or <T> ]

Comments, or not.

גשם חזק מאוד

Hebrew… Last time I tried that (the Hebrew wiki main page), NetSurf made a complete mess of it (comparing with Chrome on Android).
All the right letters, absolutely not in the right order.

I use HTML comments, but be warned that beginning a line with <!— may cause some formatting oddities in the following text.

I believe most things can be improved with tea. Or maybe beans. But mostly tea.

complete mess

Text Shaping is very complicated, but Hebrew is probably the simplest type of shaping there is (text goes right to left, numbers go left to right, punctuation adapts to text direction).

My plan for FM4 (FontManager) is to insert HarfBuzz into the FontV vector just before the FM4 layout/metrics/render layer, but it is not a trivial job. Quite apart from the text segmentation and bidirectional handling, it will have to be protected from all the rich FM control codes, and its output will have to be recombined into a font string that Paint/ScanString is still happy to process.

I continue to prototype, but the plan is to get to the point that semantically-ordered text can be thrown at FM and the correct typographic result will happen, without any typographic smarts in the calling application (often the Wimp).

…amanfrommars1…?

:-)

:-þ I’m as human as the median user.

Ah, you missed the stream of pish that was deleted!

I’m as human as the median user.

As in separating the greater from the lesser beings? ;)
Obviously we can’t call you mean.