fix: default to localized date formatting #1552
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
David-Guillot
changed the title
David-Guillot
changed the title
|
David-Guillot
force-pushed
the
patch-1
branch
from
53c9aab to
63ae0a1
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change? What problem does it solve?
On a multilingual blog with translated posts, a non-English post displays an English-formatted non-English date like
juillet 8, 2024instead of8 juillet 2024as it should be for French.This PR changes the
post_metapartial template to leverage Hugo's time.Format function's preset formats. I have chosen:date_longsince it's the one that was hard-coded here before.Was the change discussed in an issue or in the Discussions before?
Closes #1611. Is an alternative implementation of #1111.
PR Checklist