afiw/MEOW-Spec
1
0
Fork 0
forked from linuxposting/MEOW-Spec
Code Pull requests Activity

Add and fix some stuff cause im a big dumy

Browse source
This commit is contained in:
cælōrum spectātrīx 2026-03-01 00:24:39 +01:00
parent 05e73ad3c0
commit e5ab08cc6d
1 changed files with 16 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

21
RFCs/rfc-0002.ms
View file

@ -93,6 +93,11 @@ applicable. Other formatting directives in the sequence SHOULD NOT be interprete
.PP .PP
Clients running in a terminal emulator MAY instead display the text with a changed background colour, or Clients running in a terminal emulator MAY instead display the text with a changed background colour, or
without any special markup. without any special markup.
.NH 2
Overstruck text
.PP
A U+007E TILDE character, followed by a sequence of characters terminated with another tilde SHOULD be
interpreted by rendering the characters between the delimiters overstruck, if applicable.
.NH .NH
Advanced text styles Advanced text styles
.NH 2 .NH 2
@ -115,6 +120,12 @@ except that the background colour should be changed instead.
.PP .PP
Implementations SHOULD support the following symbolic colour names if they support displaying coloured text at Implementations SHOULD support the following symbolic colour names if they support displaying coloured text at
all: black, red, green, yellow, blue, magenta, cyan, and white. all: black, red, green, yellow, blue, magenta, cyan, and white.
.NH 2
Spoilers
.PP
A U+007C VERTICAL LINE character, followed by a sequence of characters terminated with another vertical line
SHOULD be interpreted by rendering the characters initially hidden, only revealing them when the user explicitly
interacts with the text area by e.g. clicking it or using a client command.
.NH .NH
Links and references Links and references
.NH 2 .NH 2
@ -156,17 +167,17 @@ Unordered lists
A U+002B PLUS SIGN as the first character of a line SHOULD be displayed as a bullet point (possibly as U+2022 A U+002B PLUS SIGN as the first character of a line SHOULD be displayed as a bullet point (possibly as U+2022
BULLET), if applicable. Any UNICODE whitespace characters directly following it SHOULD be intrepreted, and BULLET), if applicable. Any UNICODE whitespace characters directly following it SHOULD be intrepreted, and
multiple consecutive lines beginning with the character MAY be visually grouped as a list. multiple consecutive lines beginning with the character MAY be visually grouped as a list.
.NH 2
Ordered lists
.PP
A sequence of lines beginning with strictly increasing numbers followed by a U+002E FULL STOP character MAY be
visually grouped as a list by clients. The numbers themselves SHOULD NOT be changed.
.NH 3 .NH 3
Rationale Rationale
.PP .PP
Using asterisks for bullet points/unordered lists is more common in other markdown languages, but as asterisks Using asterisks for bullet points/unordered lists is more common in other markdown languages, but as asterisks
are already used for italic text, this would substantially complicate parsing. are already used for italic text, this would substantially complicate parsing.
.NH 2 .NH 2
Ordered lists
.PP
A sequence of lines beginning with strictly increasing numbers followed by a U+002E FULL STOP character MAY be
visually grouped as a list by clients. The numbers themselves SHOULD NOT be changed.
.NH 2
Code blocks Code blocks
.PP .PP
Three or more U+0060 GRAVE ACCENT characters at the beginning of a line should be interpreted as starting a Three or more U+0060 GRAVE ACCENT characters at the beginning of a line should be interpreted as starting a