Server: Configurable date/time format

[Florux 32]

Hi,

 

It would appear as though the date format is hard coded to US month/day/year. 

What would be nice is to keep the English language, but still be able to decide what date and time format to be used consistently throughout the solution. As a European user, I'd for instance like it to be DD-MM-YYYY instead. If this is only tied to the locale, one could risk having to use a non-English language in order to get the right date/time format, and that would be somewhat unfortunate..

 

Would that be an idea?

[Luke 39408]

in the web client it's actually determined by the browser/system settings

[Florux 32]

Thanks Luke!

 

Would you be able to direct me to where I might have it wrong then, as I get the date format correct pretty much everywhere else, but on Media Browser webclient I consistently get the month/day/year format on Media Browser only, and nowhere else..

 

Having said that, I also get the 12h AM/PM on this forum instead of 24h clock, so it's entirely possible something is wrong on my end. Funny thing is just that I've never had this problem anywhere else before with this computer/client, and it's also consistent across other computers and tablets, all consistently showing the US format across Windows, Mac, Linux and various tablets.

 

Here's how it looks in the web client, with US version of October 1st 2014:

 

 

And here are the local settings, causing it to be right on most other systems:Thanks again for looking at this - much appreciated!!

 

 

 -Florux

[mvheezik 2]

Hi Florux,

 

did you figure this one out? I'm having the same problem.

 

--

Martijn

 

 

 

[Luke 39408]

@@mvheezik can you please describe your issue in more detail? thanks !

[spikemixture 3]

Has this been fixed.

 

I have bought the Premiere version for 12 months to give emby a real go against it's competition.

 

One annoyance is the date thing.

 

I am looking at the Release date Format box.

 

yyy.MM.dd 
 

It has a drop down but that gives no other option.

 

Developers from the US really must realize that the US is not the 'World"

 

300 million in the US use yyy.MM.dd
7+ Billion do NOT.

[Luke 39408]

@@spikemixture, actually we are using a date input box, and your browser is choosing to display it that way. So i think what you really mean to say is your browser vendor must realize that the US is not the world

 

Have you configured your system time zone settings correctly? What browser and version are you using?

[spikemixture 3]

@@spikemixture, actually we are using a date input box, and your browser is choosing to display it that way. So i think what you really mean to say is your browser vendor must realize that the US is not the world

 

Have you configured your system time zone settings correctly? What browser and version are you using?

Hey Luke

 

I have all my settings to non US. Because like 90% of the world's population I do not live in the US!

 

The only place now that appears to have the US only settings is where I stated in my post.

The dates are set correctly (for me) in all other locations so it really doesn't matter .

 

Thanks for the reply...

 

[Luke 39408]

Ok so then that is just an issue of how the browser is presenting it's date input field. Thanks.

[spikemixture 3]

So almost another year has passed 

 

And we all have to put up with the US take on the world  yyyy-MM-dd

 

 

 

I should not have paid the lifetime membership ! 

Edited January 14, 2020 by spikemixture

[seanbuff 1054]

I think there is some confusion in this thread. Firstly the OP @@Florux was referring to a displayed "release" date on a details page.

 

@@spikemixture the release date you are referring to is only used within NFO files and should not reflect how any date is 'displayed' in the UI. (And contrary to what you think, yyyy-MM-dd is not a US date format, it's more of a Korean or Chinese one in fact.)

So the date used here should not bother you, unless you are manually opening NFO files and viewing their content.

 

@@Luke the field that spikemixture is talking about is not a browser date input box, but rather a hard-coded format presumably based on Kodi NFO date format standards once upon a time.

 

Back to the original topic, I also raised this as an issue here: 

https://emby.media/community/index.php?/topic/80930-added-does-not-respect-machine-locale-whereas-metadata-does/

 

@@SamES explained the problem well. @@Luke seems there is some work to be done for other English speaking countries outside of the US and UK.

 

tl;dr - as SamES explained in the other thread, until @@Luke comes up with a more permanent solution - the current workaround here is to set your 'Preferred Display Language' in Emby to 'English (United Kingdom)'

 

 

[Luke 39408]

Yes he is correct regarding release date. That option is used to indicate the date format in your nfo files, as it says right there in the help text.

[Luke 39408]

Many of our apps have a date time locale option. I would suggest exploring that.