allowing uaSymbol on undefined dates
eroux opened this issue · 4 comments
First, thanks for this very useful library!
Currently the code allows 18? to represent "19th century, uncertain", but not 18XX?, as exemplified in this sandbox. I can't really see 18XX? allowed or forbidden in part2 of the draft, but neither can I see 18? forbidden or allowed (even in the grammar at the end)... is there a reason one works and not the other?
Good question. I don't think that qualified and unspecified dates are supposed to be combined. About the century short-hand I'm not sure either: I guess that it's probably not intended to be qualified either, but the way the API is designed (with Century being a inheriting from the extended date base class) would have meant artificially limiting the interface for the Century sub-class -- I think that's probably why I decided to have the parser accept strings like 18?. In the grammar there are similar reasons: it would probably take more effort to exclude centuries with uncertainty qualifiers than to accept them.
Thanks for your answer! Do you have contact we could ask about this? Otherwise I think I can ask some people in my network but it will take time
Sorry, no. Great if you could find out more!
Ok, I'll keep you updated