Christian Neumanns

> I think the best way to avoid confusion is to not say anything beyond "a CSS file" Yes, ok. > I've come across a few places where it mentions...

> the problem here is that PML is not aimed at software engineers but writers, so any assumptions regarding such specialized jargon are misplaced. Indeed. Good point! > The `[text`...

In the upcoming PMLC version 3, the following rule is applied: - All block nodes (including the `doc` node) have an optional `id` attribute. - Inline nodes don't have an...

> What's important though is that the documentation clarifies the idiomatic way of providing section-IDs for cross-referencing I've added the following note to the chapter's description: "The idiomatic way of...

The reference manual and user manual are both already bundled with the distribution. They are stored in the following sub-directories of the distribution: docs\ref_manual\index.html docs\user_manual\index.html However, note that the location...

> It would be nice if PMLC help will also print information about the location of these folders and files In the new version I've already implement a new CLI...

> the line code for the escape character is forced to contain a trailing space Well spotted! The reason is that the current parser uses a regex that does not...

> the line code for the escape character is forced to contain a trailing space (\ ) — in the source file This bug has been fixed in version 2.0.0

> The line `An [c\[admon]` block raises a conversion error: Yes, because it's invalid syntax. > Forcing to change the line to `An [c \[admon]` block. That's the correct way...

> the problematic aspect here is the definition of whitespace character Yes, unfortunately there is no universal standard definition for 'whitespace'. To keep it simple, a whitespace character after a...