Skip to content
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

Remove misleading calendar model output #59

Merged
merged 1 commit into from
Apr 16, 2015
Merged

Remove misleading calendar model output #59

merged 1 commit into from
Apr 16, 2015

Conversation

thiemowmde
Copy link
Contributor

This patch simply removes the discussed, confusing calendar model display from this formatter. It's split from #49 (and will cause merge conflicts, but I would like to discuss the two changes in two independent pull requests).

Note that this formatter is currently unused. The Wikibase UI uses the HtmlTimeFormatter instead (which, by the way, uses the calendar model as "actual" and not "preferred calendar").

This patch also removes dead code that is not used anywhere, most notably the redundant language option.

@thiemowmde thiemowmde added the bug label Apr 14, 2015
@thiemowmde thiemowmde added this to the 0.7 milestone Apr 14, 2015
brightbyte pushed a commit that referenced this pull request Apr 16, 2015
Considering that giving no calendar model is treated as equivalent to saying "gregorian" by the time parser, it should be safe to remove "gregorian" from the output. I was going to suggest to hold this patch back until we have a decision on the interpretation of the calendar model, but it seems pointless: if the interpretation is that the timestamp is always gregorian, then omitting the calendar in the output makes no difference; if the interpretation is that the timestamp depends on the calendar model identifier, then outputting "gregorian" indiscriminately would be wrong.
@brightbyte brightbyte merged commit d7bee43 into master Apr 16, 2015
@brightbyte brightbyte deleted the nonGreg branch April 16, 2015 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants