Closed snomos closed 2 years ago
Probably it would be best to parameterise the single line comment character based on file type, so that whatever the comment character is, it should be doubled to start a doc comment.
If done this way it would be easy to support new file types.
Mm, the scripts worked somewhat for VISL CG3 files by accident, I've split code into separate handlings since there's not much actually shared between the formats
The main culprit is that CG uses
#
as the comment character, whereas the other source files we extract from are using!
. This leads to#
being part of the extracted text after!!=
and!!≈
. That is not desirable.Example:
comes out as:
which looks like this in the final output:
Err/Orth
:Err/Orth #
Err/Orth-a/á #
Err/Orth-nom/gen #
Err/Orth-nom/acc #
Err/DerSub #
Err/CmpSub #
Err/UnspaceCmp #
Err/HyphSub #
Err/SpaceCmp #
Err/Spellrelax #
err_orth_mt #
We don't want the
#
there 😄