-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
differentiate human readability between uncertain month and day #78
Comments
is the expression "June 11th, 1904 (day uncertain) " and "June 11th, 1904 (month uncertain)" the desired output ? Also, in this case, where the human readable date is surrounded by parentheses by the interface or outer script, you would have double parentheses -- like "(June 11th, 1904 (day uncertain))" -- which is perhaps undesirable, so in this case to use a dash is the only viable typographical solution? |
by the way we can work on a solution like the following (taking French as reference) "edtf-maybe": "$1 (incertain)", becomes: where the content of the parenthesis is probably given by another message $2 |
Hi Thomas, I can't speak to the code, that is not my task here. I think that thinking wise you are on the right track. See also https://www.loc.gov/standards/datetime/ for some additional guidance Each Y,M,D can three types of qualifiers: ? ~ and % Depending on where the qualifier is added the humanisation differs but you can also have the qualifier on the right side I think we need a new translation string for each of the possible cases |
ok, for now we are covering some of them, hope to cover all the combinations soon |
Currently all uncertainty is being used as a catch all so the human readable version of an uncertain month translated to the same string as the uncertainty of a day.
The text was updated successfully, but these errors were encountered: