You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per upstream issue 296, each Junk should end whenever a new line begins with a single character that could be the start of a new Entry (i.e. ^[-#a-zA-Z]). This is working correctly only in the case of potential Comment entries (see comments.ftl where the leading # starts a new Junk) but is incorrect for all other cases such as possible Messages and Terms (see unclosed.ftl which should result in 4 Junks but instead merges 6 junk_lines into 1 Junk).
Note the JavaScript implementation has the same bug.
The text was updated successfully, but these errors were encountered:
Per upstream issue 296, each
Junk
should end whenever a new line begins with a single character that could be the start of a newEntry
(i.e.^[-#a-zA-Z]
). This is working correctly only in the case of potentialComment
entries (see comments.ftl where the leading#
starts a newJunk
) but is incorrect for all other cases such as possibleMessage
s andTerm
s (see unclosed.ftl which should result in 4Junk
s but instead merges 6junk_line
s into 1Junk
).Note the JavaScript implementation has the same bug.
The text was updated successfully, but these errors were encountered: