prko

Congratulation! I still have no success... Here is my error report when building through the following terminal commands: ``` cmake -DCMAKE_CXX_FLAGS="--std=c++17 -Wno-enum-constexpr-conversion -D_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION" -DCMAKE_PREFIX_PATH=`brew --prefix qt5` .. cmake --build ....

@capital-G Thanks! I removed all packages installed by brew and brew itself, then reinstalled them. Now it seems to work. There are still lots of warnings and errors, but I...

The following list contains the same bug: - https://doc.sccode.org/Classes/HistoryGui.html: 'doc'-related - https://doc.sccode.org/Classes/IdentityDictionary.html: 'parent' and 'proto' variables - https://doc.sccode.org/Classes/LID.html: LED's - https://doc.sccode.org/Classes/SimpleNumber.html: Owen's T Function - https://doc.sccode.org/Classes/SynthDef.html: Wrapping Example: 'factory' production...

Converted PDF from the corresponding reference in SCDoc included in this PR: - [Various punctuation marks for non-code text _ SuperCollider 3.14.0-dev Help.pdf](https://github.com/supercollider/supercollider/files/15053083/Various.punctuation.marks.for.non-code.text._.SuperCollider.3.14.0-dev.Help.pdf) - [Various punctuation marks for non-code text...

@JordanHendersonMusic The bugs described in #6278 can be avoided with this PR. The complete list of the same bug in built-in core schelp files: https://github.com/supercollider/supercollider/issues/6278#issuecomment-2085738183

In this PR, `_` is used to enable various punctuation marks, but a word starting with `_` is related to primitives by its colour. This can be a bit confusing...

Converted PDF from the corresponding reference in SCDoc included in this PR: [Non-code punctuation marks and symbols _ SuperCollider 3.14.0-dev Help.pdf](https://github.com/supercollider/supercollider/files/15344415/Non-code.punctuation.marks.and.symbols._.SuperCollider.3.14.0-dev.Help.pdf)

> Also, the schelp file could be formatted with a bit fewer blanklines I have reduced the number of blank lines. > is sccdoc not UTF-8 compatible? > Does this...

@capital-G Thanks for your opinion! I am familiar with what you mentioned. Why I wanted to implement it was for the following reasons: - On Windows and Linux, using character...

See how this works: