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
I'm baffled about how consecutive punctuation is expected to be handled; the test suite seems to do different things in different places, and often those things seem strange.
For example in affix_WithCommas.txt, ,; seems to collapse to ,, but in punctuation_FullMonty*.txt it stays ,;.
I can't think of a case where I'd actually want to see ,; -- and it seems to me that collapsing to ; makes more sense than collapsing to ,.
The text was updated successfully, but these errors were encountered:
Sorry for the delay in responding. (I've turned on notifications now.)
In affix_WithCommas.txt, the comma is the leading character of a user-supplied suffix, and overrides the style-supplied delimiter. The CSL Specification doesn't say anything about user-supplied suffixes, but overriding the delimiter seems the right thing to do there.
In punctuation_FullMontyPlain.txt, both punctuation marks are supplied by the style, so collapsing rules are applied, which mostly just aim to avoid duplicate punctuation. (The controlling map in citeproc-js is here in case it's useful.)
I'm baffled about how consecutive punctuation is expected to be handled; the test suite seems to do different things in different places, and often those things seem strange.
For example in
affix_WithCommas.txt
,,;
seems to collapse to,
, but inpunctuation_FullMonty*.txt
it stays,;
.I can't think of a case where I'd actually want to see
,;
-- and it seems to me that collapsing to;
makes more sense than collapsing to,
.The text was updated successfully, but these errors were encountered: