-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allowing uaSymbol on undefined dates #41
Comments
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 |
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 |
First, thanks for this very useful library!
Currently the code allows
18?
to represent "19th century, uncertain", but not18XX?
, as exemplified in this sandbox. I can't really see18XX?
allowed or forbidden in part2 of the draft, but neither can I see18?
forbidden or allowed (even in the grammar at the end)... is there a reason one works and not the other?The text was updated successfully, but these errors were encountered: