La bonne nouvelle, c’est que j’ai été un bon garçon et que j’ai utilisé la recherche pour trouver une réponse à mon problème. La meilleure nouvelle encore, c’est que j’ai découvert que cela a été abordé à de nombreuses reprises. Et voici une autre bonne nouvelle : les sujets que j’ai trouvés pointaient tous vers la même page pour la réponse. La mauvaise nouvelle, c’est que cette page n’est plus disponible
Donc, à regret, je vais poser ma question ici.
Où dois-je définir le format de date pour éviter cette bizarrerie entre « 12 fév. » et « 12 février » ? J’ai également consulté les paramètres et vu diverses options, mais il n’est pas clair laquelle je devrais modifier.
Et, juste pour provoquer, quelle est la logique derrière ce format de date par défaut plutôt déroutant (voir ci-dessus), étant donné qu’il y a eu pas mal de commentaires au fil du temps indiquant que c’est confus.
Thank you, Jeff. It’s not too easy to distinguish topics that are wildly out of date :), given that the one you reference is almost 4 years old.
I did see that topic but it seemed like a bit of a hack. A string with “tiny” in the name feels like it should use YY. Modifying it to use YYYY may resolve one issue, but could have unintended consequences elsewhere, where it might be the preferred string precisely because it’s “tiny”.
Without knowing too much yet about where I’d make this change, I’m guessing a better approach would be to find the HTML that currently references the tiny string for post date and modify that to instead use the long form. I don’t know enough yet, though, to know where to do that and whether that makes the change vulnerable to product updates later.
What I do know is that I’m really not a big fan of that weird date format
Not trying to be argumentative, Jay, but why is changing the tiny string definition to use the long form and then hunting around to find / test other references to that string easier than simply changing the relevant template to use the appropriately named long form?
The former seems rather cumbersome for what seems like a simple change.
Are there issues with updating the “template” (not sure if Discourse used that term) to use the preferred format?
Changing the value in the web interface is easy and doesn’t require you to override the template, which has lots of other stuff in it, that might change in the future. It is reasonably likely that nothing will break, and if it does, the css you’d change in a theme is exactly what you’d do by overriding the template. Further, if you override the template and it changes in the future you’ll have to find out that it changed and fix your version whenever that happens.
This is simply editing text in the same way you would edit text anywhere in Discourse via Admin, Customize. It is not risky at all and cannot be “broken” by updates. It is the simplest and easiest way to achieve the customization you desire.
