Zoltán Lehóczky

The configuration can be part of the codebase (in Directory.Build.props, ruleset and editorconfig files). If we'd write our own analyzers then that could would most possibly need to be a...

Coding style guidelines added here: https://github.com/OrchardCMS/OrchardCore/pull/10724

The Archive Later behavior doesn't seem to be deliberate, no. But Hisham, you've written that, please chime in.

The server perhaps shouldn't customize the date format but the app should never rely on the server's configuration (apart from the basic runtime requirements) either. So just as we don't...

Which part of `Accept-Language: en-US,en;q=0.5` specifies a short date format?

The problem is not the culture. The problem is a date format _within the specified culture_. It's all en-US but depending on the server's settings, the same en-US culture can...

That we know. The point of this issue is being able to configure the date time format used by Orchard for a given culture to be reliably exactly the same...

I don't see why we'd hack the ASP.NET Localization middleware. This is about changing the behavior of `CultureScope`, part of Orchard. It's already an Orchard-specific concept. But even if we...

@ns8482e I don't want to change this on the server. In fact, this is something out of my control (while Dávid mentioned our CI server, the problem is not its...

What issues do you mean? Just to clarify, I'm not against changing this format. I'm for being able to change it _in Orchard_. While having consistency across different OS families...