testing above guide

Literal

Redtext
``Italics``
```Bold```

Code

$$Fancy$$ $$Italics$$
spoiler
dice (1)d(20)
$$\color{red}{redtext}$$
$${\hugeHUGETEXT}$$
$${\bigBIGTEXT}$$
$${\smallSMALLTEXT}$$
$$\tiny{TINYTEXT}$$

Potential Alternatives/Fixes
Italics
Bold
$$\color{red}{redtext}$$
$$\huge{HUGETEXT}$$
$$\big{BIGTEXT}$$
$$\small{SMALLTEXT}$$
$$\tiny{TINYTEXT}$$

>>5597
Am I that stupid or is the FAQ page really no where to be found???

Testing
—————————————–
redtext
italics
bold
spoiler
__underline__
%%highlight%%
—————————————-
< etouQ
> Quote
[gurochan.cx/ Link text]
—————————————

=three equals=

>>19472

Wasn't able to replicate the full width line break from >>5597, or the big header from >>5708.

I suppose italics, bold, and subheading redtexts are good enough.

>>19246
That was a post from 2016, the faq was lost somewhere while gchan was dying and rezzing over the years.

test inline ==red text==

Just to be sure

two single quotes

three single quotes

Partitions

Test if the line can continue after a header

==Header== more text on the same line

===Testing=== Header

=Testing Header=

Testing Header

–test–
test
##test##

Seeing that the software has changed, let's do some more testing:

This is italic (two single quotes before and after).

This is bold (three single quotes before and after).

This is a headline (two equals signs before and after)

Awesome! Some more testing.

> this is a quote (greater-than sign before text)

< this is another kind of quote (less-than sign before text)

=This is a smaller headline (three equals signs before and after)=

This text is __underlined__ (two underscores before and after).

This is ~~striked out~~ (two tildes before and after).

This is a spoiler (two asterisks before and after).

This uses a

monospaced font

("code" in square brackets before and "/code" in square brackets after).

So most of these didn't work, but others did. All right, good to know.

One final text.

''I wonder whether
stuff like italics
can span multiple lines?''

testing horizontal line break

——————

testing horizontal line break

testing italics (bbcode)
testing <i>italics</i> (html)
testing italics (double apostrophes)

test

I just wonder, why after so much testing not one post summarizes all known formats and provides the needed codes.

Some are well documented, but don't list all options. Some list a lot of options, but don't show the codes. And some are only test suits and still provide codes that don't work.

Well, this post may also not be complete, because there are still some questions. But it assembles all available knowledge from this thread and some further testings.

=​=Headline=​= (2 equals signs) soley on a line gives
Headline
'​'italic'​' (2 apostrophes) gives italic.
'​'​'bold'​'​' (3 apostrophes) gives bold.
*​*masked*​* (2 asterisks) gives masked and reveals the text when hovered with the mousepointer.
Italic, bold and masked can be nested.

<​-​- (less-than sign + 2 hyphens) combine to ← (left arrow)
-​-​> (2 hyphens + greater-than sign) combine to → (right arrow)
-​- (2 hyphens) combine to – (short dash)
-​-​- (3 hyphens) combine to — (long dash)

>at the beginning of a line gives a quote.
​>​> with the number of an existing post gives a link to that post, like >>5708, where 40 hyphens resulted in a horizontal line. It seems, that this is not longer working.

If someone knows how to create the centered Headline in >>5597, the information would be appreciated. The same applies to other formatting codes.

I just learned that the short links >>24107 only work in the same category. To link into another category >>44797 you have to type the long form, e.g. https://boards.guro.cx/3dcg/res/43846.html or https://boards.guro.cx/3dcg/res/44797.html#44957.

>>24161
It's called board, not category.

Also you can link from other boards like this: >>>/3dcg/44957

>>24166
that post was deleted so here is another example: >>>/3dcg/45317

I tried to post, but I was categorized as spam. How do I fix that? And yes, I am no spammer.

>>24166
>It's called board, not category.
Oh, little silly me! TY for pointing out.
Obviously I was thinking categorically in other categories. :)

I tried it with only two angle brackets, hence I had no success. So TY too for this information.

We can summarise:
A link to a post in the same board is made with two closing angle brackets. >>24166
A link to a post in a different board is made with three closing angle brackets. >>>/3dcg/45317
In both cases the link becomes a comment at the very beginning of a line or plain text at any other position if the number of brackets does not corespond to the kind if link or – regardless of the number of brackets – the destination does not exist.

Formatting continued …

I recently found this:
.​.​. (3 dots) combine to … (horizontal ellipse)

@admin
Today I reviewed some older posts and found some that where not an opening post but like an opening post had a subject. I recalled that I had used this feature myself ( >>/3dcg/42648 ). I also remembered that this happened before the change of the board software/configuration. It was very convenient for tracking corresponding posts inside a thread. Would you please consider to reenable this feature or to explain the reason why it is disabled?


Another thing I'd like to ask for is a little help to complete my list of formatting strings ( >>24107 with >>24215 and >>24216 ). Would it be possible to get information about the relevant section of the configuration file (I assume inc/instance-config.php)? If there are board specific configuration files (like <board>/config.php) it may help to learn about their relevant content too. If you have security concerns please tell me – may be it's possible to find a solution.

>>24468
This is an old version of vichan (which we can't upgrade because it's highly modified), so titles are only for opening posts
As for formatting strings, you seem to already have found all.

Is it allowed here to post stories in other languages than English? I'm not confident in my English writing skills, but I still want to share with those, who understand Russian or willing to autotranslate.

>>24957
There are at least a few German stories posted (although they're from a few years back, so it was a previous iteration of gurochan with different administration), although under one of them an anonymous complains and asks to at least keep them all in one thread to not flood gurochan with non-English threads, which sounds reasonable.

Seeing how there's no reply here from administration yet, I'd say just go for it, but keep your stories neatly in one thread. The worst that can happen is that the admins will finally notice you and give a proper no by deleting the thread.

>>5597
The hunt for the huge header continues. At minimum, other people will know not to try these:

Test spaces between text and double equals signs

$Test
$ Test

$Test$
$ Test $

$$Test
$$ Test

$$Test$$
$$ Test $$

#Test
# Test

#Test#
# Test #

##Test
## Test

##Test##
## Test ##

^Test
^ Test

^Test^
^ Test ^

&Test
& Test

&Test&
& Test &

+Test
+ Test

+Test+
+ Test +

++Test++
++ Test ++

<h>Test<\h>
<H>Test<\H>
<header>Test<\header>
<Header>Test<\Header>

\h Test
\H Test
\header Test
\Header Test

Test four leading spaces

:Test:
::Test::
:::Test:::
::::Test::::

'Test four single quotes'

|Test|
||Test||
|||Test|||
||||Test||||

A few more attempts:

{\h Test}

{\h} Test

{h}Test{\h}

{\header Test}

{\header} Test

{header}Test{\header}

[\h Test]

[\h] Test

Test[\h]

[\header Test]

[\header] Test

[header]Test[\header]

!Test!

!!Test!!

—-
Test

Test
—-

____
Test

Test
____

====
Test

Test
====

# Test 1
## Test 2
### Test 3
#### Test 4
##### Test 5

=header=

header

=header=

==header==

Test
1. One
2. Two
3. Three

This is a test, like all the other posts here.

> Quote.
Comment.

> Quote.

Comment

I'm sorry if spam, just trying out
<----
<--
<-
A
#A
##A
###A
@A

It looks like there were changes in the conversion process since I posted >>24107.


The basic codings still work:

=​=Headline=​= (2 equals signs before and after the text) soley on a line gives a
Headline

'​'italic'​' (2 apostrophes before and after the text) gives italic.
'​'​'bold'​'​' (3 apostrophes before and after the text) gives bold.
*​*masked*​* (2 asterisks before and after the text) gives masked and reveals the text when hovered with the mousepointer.
Italic, bold and masked can be nested.

​> (one closing angle bracket) at the beginning of a line gives a quote.
> Anticonfusion hint: The characters of the describing samples are enclosed in "Zero Width Spaces" (&#8203;) to prevent the conversion.
​>​> (two closing angle brackets) with the number of an existing post in the same board gives a link to that post, like >>5708. (There resulted 40 hyphens in a horizontal line, but it seems, that this is not longer working.)
​>​>​> (three closing angle brackets) are used to link to an existing post in a different board, >>>/3dcg/45317.
Caution: The links become a quote at the very beginning of a line or plain text at any other position if the number of brackets does not corespond to the kind if link or – regardless of the number of brackets – the destination does not exist.



Like the centered header in >>5597 (for this see also >>24764) and the horizontal line in >>5708 the conversion of special strings to single characters is now disabled.
Unfortunately using the entities at the end of the lines also doesn't work. But the characters can still inserted by copy and paste.
Just get them from this post or — like other characters — from the character table programm on your computer or phone.

<​-​- (less-than sign + 2 hyphens) formerly combined to ← (leftwards arrow) (&#8592;).
-​-​> (2 hyphens + greater-than sign) formerly combined to → (rightwards arrow) (&#8594;).
-​- (2 hyphens) combined to – (short dash AKA en dash) (&#8211;).
-​-​- (3 hyphens) combined to — (long dash AKA em dash) (&#8212;).
.​.​. (3 dots) combined to … (horizontal ellipses) (&#8230;).


You are still invited to provide information about formatting codes to be added.

After the recent software change the next update is neccessary.
The new software doesn't support most of the old formatting codes anymore. Instead it interprets the well documented bbcode (Bulletin Board Code, introduced 1998, see Wikipedia). Unfortunately it uses only a (very) small subset. Only six tag pairs are recognized, of which two have (at this moment) no effect.

​This are the fully working tags:
[​b​]​{text}​[​/b​]​
  {text}
  Makes {text} bold
​[​i​]​{text}​[​/i​]​
  {text}
  Makes {text} italic
​[​u​]​{text}​[​/u​]​
  {text}
  Underlines {text}
​[​code​]​{text}​[​/code​]​
  

{text}

  Meant for rendering code snippets

This are the working tags without function:
​[​s​]​{text}​[​/s​]​
  {text}
  Should create a strikethrough on {text}
​[​spoiler​]​{text}​[​/spoiler​]​
  {text}
  Should Creates a spoiler section (a box) that is by default collapsed until you click a button or the box itself to expand it to show the {text}

From the old tags has only the board internal linking survived:
>​> (two closing angle brackets) with the number of an existing post in the same board gives a link to that post, like >>5708.
​The links are striked through if the destination does not exist.

The two other closing angle bracket tags seem to be switched off:
> (one closing angle bracket) at the beginning of a line gave a quote.
>​>​> (three closing angle brackets) were used to link to an existing post in a different board, >>>/3dcg/45317.
As you can see, there is no more formatting or link action. At this moment I again know only the the long form, e.g. https://boards.guro.cx/3dcg/res/43846.html or https://boards.guro.cx/3dcg/res/44797.html#44957, to link to other boards.


Anticonfusion hint: The characters of the describing samples are preceded by, interrupted by or enclosed in "Zero Width Spaces" (&#8203; or &#x200B;) to prevent the conversion.
Because of their nature you can't see these characters, but you can detect them indirect: It takes more than one stroke of the cursor left or right keys to move the cursor from one viewable character to the next.
You can test this here: 123456 (no Zero Width Spaces, six keystrokes), 12​45​​89 (one Zero Width Space between 2 and 4, two Zero Width Spaces between 5 and 7, nine keystrokes)
To copy Zero Width Spaces it is helpful to include the leading and following characters and delete these after inserting.
​

Special characters like arrows (←, →), horizontal ellipses (…), dashes (–, —) or even Zero Width Spaces (​) can still be inserted by copy and paste. Just get them from an old post or — like other characters — from the character table programm on your computer or phone.
Hint: It is always a good idea to check if the operation worked as intended. Sometimes characters are altered while moved to or from the clipboard. And sometimes different characters just look like they are the same, because they are presented similar by a program.


You are still invited to provide information about now working, reenabled or (for the archive) "historical" formatting codes to be added.

The code list at https://boards.guro.cx/static/html/bbcode.html lists six formatting tag pairs:

​[​h​]​{text}​[​/h​]​
{text}
Formats {text} as headline.

​[​b​]​{text}​[​/b​]​
{text}
Makes {text} bold.

​[​i​]​{text}​[​/i​]​
{text}
Makes {text} italic.

​[​u​]​{text}​[​/u​]​
{text}
Underlines {text}.

​[​s​]​{text}​[​/s​]​
{text}
Creates a strikethrough on {text}.

​[​spoiler​]​{text}​[​/spoiler​]​
{text}
Masks {text} until it is marked or the mousepointer hovers over it.


There are some additional tags available:

​[​code​]​{text}​[​/code​]​

{text}

Renders {text} as code snippet.
​
​> (a closing angle bracket) at the beginning of a line renders this line
> with a quote color,
​< (a opening angle bracket) at the beginning of a line renders this line
< with another quote color.

​>​> (two closing angle brackets) directly followed (i.e. no blanks between) by the number of an existing post gives a link to that post, like >>5708. Unvalid links are striked through.
Since the posts are globally numbered it should be theoretically possible to link into other threads and boards, but it seems that this works only partly at this moment. There are links with a “Cross-thread”-flag that are working, although there is a pop-up message “Quote source not found” when hovering the mouse pointer over them. “Cross-board”-links seem not to be available.

Anticonfusion hint: The characters of the describing samples are preceded by, interrupted by or enclosed in "Zero Width Spaces" to prevent the conversion.
Because of their nature you can't see these characters, but you can detect them indirect: It takes more than one stroke of the cursor left or right keys to move the cursor from one viewable character to the next.
You can test this here: 123456 (no Zero Width Spaces, six keystrokes), 12​45​​89 (one Zero Width Space between 2 and 4, two Zero Width Spaces between 5 and 7, nine keystrokes)
To copy Zero Width Spaces it is helpful to include the leading and following characters and delete these after inserting.


You can insert special characters like arrows [← (U+2190), → (U+2192)], horizontal ellipses [… (U+2026)], dashes [– (U+2013), — (U+2014)] or even Zero Width Spaces [​ (U+200b)] ‒ to be precise all characters ‒ by typing their Unicode value (U+….) as Alt-codes in Windows or as Ctrl+Shift+U-sequence in Linux. It would be to escalating to explain the methods in detail. Do a search in the internet and you’ll find more than enough tutorials. You’ll learn all about which steps are to take and which limitations apply. Just one note: The input values have to be hexadecimal. It might be necessary to force Windows to accept hex-Alt-codes by activating an option in the registry ‒ look up its name “EnableHexNumpad” in the internet.
You also can copy and paste. Get the characters you want from an old post or ‒ like other characters ‒ from the character table program on your computer or smartphone.
Hint: It is always a good idea to check if the operation worked as intended. Sometimes characters are altered while moved to or from the clipboard. And sometimes different characters just look like they are the same, because they are presented similar by a program.


You are invited to provide information about now working, reenabled or (for the archive) "historical" formatting codes to be added.

test

test

to the admins:

When I click on "Comment too long, view post No..... to see the full comment" the full comment don´t open.

in the Literature section, clicking on the 'comment too long click to read the full comment' doesn't work, and just repeats the screen with the short comment.

The long post issue should be good now: >>>/dis/25198

Sorry we didn't notice it quicker