- Fixed broken backward compatibilty introduced in v2.6.2 (issues referenced in #148, #147, #143).
- Fixed: Take an erroneous format string like
"this is {uncomplete"
(missing closing brace). Before v2.7.0 the parser handled{uncomplete
as aTextLiteral
, not as an erroneousPlaceholder
. - Fixed: Since v1.6.1 there was an undiscovered issue: If the
Parser
encountered aParsingError.TooManyClosingBraces
, this closing brace was simply "swallowed-up". This way, the result withParser.ErrorAction.MaintainTokens
differs from the original format string. From v2.7.0, the redundant closing brace is handled as aTextLiteral
. - If you have issues formatting HTML with CSS and/or JavaScript included, please read the bullet-proof How-to in the Wiki