set to use system default date format, but not correct date display in client file list

[imprintz]

I have just updated FZ client to new version, noticed that the date format has changed to mm/dd/yy. Before update this was dd/mm/yy as per system settings (UK, Windows 8, 64-bit). Checked the setting in Filezilla and the default is selected (use system default). It seems this is being ignored.

[Tim Kosse]

What's your system region country set to and which language are you using in FileZilla?

[romualdo]

Since the original poster didn't provide more information, and I have the same problem, I attached the screenshot with all relative informations visible at once. My OS is Win 7 64bit, FileZilla Client 3.9.0.5 (latest)

[Gary]

Same here. New Zealand, English (NZ), Win 8.1, FZ3.10.3 FZ set to Use System.
System date is default d/MM/yyyy, Filezilla is displaying mm/dd/yy

[Gary]

Even with short date set to dd/mm/yy Filezilla still shows mm/dd/yy

[Tim Kosse]

@romualdo: Which language have you set in FileZilla? It seems to be set to English (US), otherwise FZ would be in Croatian. If using English (US), the settings for the English (US) locale are being used, not the settings for the Croatian locale.

@garyt: I can't reproduce this. With language in FZ set to "Default system language" and Windows set to NZ, it uses the dated format of said locale.

[romualdo]

I just checked language, and no language was set, strange. I selected "Default system language" (which is English US), set Date and Time formatting to "Use system defaults" and restarted FileZilla. Everything looks just right.

I'm not sure just why does the language selection affects date/time format?

[Tim Kosse]

I just checked language, and no language was set, strange.

That's odd indeed. How old is your current installation of FileZilla, ie. which is the version you first used with your current user profile without ever deleting the settings?

I'm not sure just why does the language selection affects date/time format?

The technically correct term would be "Locale", though as most users would not understand it, it's labelled "Language" instead.

Language is a major locale component, perhaps the primary one. Other locale components are collation rules for strings and formatting rules for date/time, numbers, currencies, phone numbers, measurement units (e.g. proper meters vs. antique miles and furlongs), paper fonts and others.

[romualdo]

Replying to codesquid:

I just checked language, and no language was set, strange.

That's odd indeed. How old is your current installation of FileZilla, ie. which is the version you first used with your current user profile without ever deleting the settings?

I'm not sure now, I believe i was using version 3.9.0.5 (fresh Windows installation), but settings were backed up before reinstallation, and I regulary updated versions.

I'm not sure just why does the language selection affects date/time format?

The technically correct term would be "Locale", though as most users would not understand it, it's labelled "Language" instead.

Oh, OK now, I understand this. But still, there are separate settings for date/time format. When set to "Use system defaults", should it use system defaults or selected Language/Locale defaults?

I think that the core problem here is mislabeling. "Language" should be "Language/Locale", and for Date/Time "Use system defaults" should be "Use locale defaults".
On a side note, "Language" (or "Language/Locale") shouldn't be unselected upon installation, but set to "Default system language". This should be checked with fresh FileZilla installation, but I cannot try it right now.

[Gary]

Discrepancy between system and filezilla dates

[Gary]

Hmm - odd. I guess I can now work around it...
I've put in a screen capture for reference. Please let me know if there is anything obvious I have missed. I do have Chinese installed as a language, but I also have that at work, where Filezilla behaves. I'll double check the FZ settings there.

[Gary]

The settings for Filezilla, and the System language setup are pretty much same at work and home. The only obvious difference is that Win8 at work is an enterprise version... Is there anything else that has an impact on the date?

[Tim Kosse]

Operating system edition shouldn't make a difference.

[Gary]

Well that was fun... I manually set the date format to something a bit more useful, and the Filezilla language automatically set itself to finnish... Oh Joy...

[Tim Kosse]

Are you by chance using any Finnish third-party software that loads DLLs into other program's address space (e.g. via a shell extension) with this DLL calling the setlocale function?

That's about the only explanation I can think of.

[robadob]

I can confirm that I've also got this bug with Filezilla 3.12.0.2 on Windows 8.1 Pro x64. The 'Last modified' column in file listings and 'Time' column in transfer queue, are using the US date format (MM/dd/yyyy) despite the system date format being set to dd/MM/yyyy (English (United Kingdom)).

Can't confirm whether it was present with earlier versions as I don't look at the dates often and only installed windows on this machine a month ago.

I've just switched to using the custom format '%d/%m/%y'.

[gsfilezilla]

Same problem here :

Filezilla 3.12.0.2
Windows 8.1 (Standard) 64 bit

In Region settings :
Home location : United Kingdom
Short Date : dd/MM/yyyy
System Locale : English (United Kingdom)

Under Language :
English (United Kingdom)

Last modified date format showing in Filezilla is MM/dd/yy
I also changed to the custom format, which works fine.
By the way... Thank you :)

[adrianw]

Replying to imprintz:

I have just updated FZ client to new version, noticed that the date format has changed to mm/dd/yy. Before update this was dd/mm/yy as per system settings (UK, Windows 8, 64-bit). Checked the setting in Filezilla and the default is selected (use system default). It seems this is being ignored.

I've just updated to Filezilla Client 3.13.0 on OS X Yosemite and have exactly the same problem.
File dates are being displayed as mm/dd/yyyy instead of respecting my system setting of dd/mm/yyyy

[JamesT]

OS: Windows 10 64-bit
Filezilla: 3.14.0

My Windows locale is set to UK, date format dd/mm/yy, and File Explorer displays dates in this format. Filezilla is set to use system defaults, and yet displays dates in mm/dd/yy instead.

This has been happening over multiple Filezilla versions. Can this be fixed or are we forced to specify custom date format in Filezilla?

[Tim Kosse]

Which language do you have configured in FileZilla?

[JamesT]

Sorry for the late reply.

My language in Filezilla is set to "Default system language". I was going to try to set this manually to en_UK but it was not present in the Filezilla language list.

Filezilla is being used on Windows 10 set to UK, with Windows File Explorer correctly showing dates in dd/mm/yy format. However, Filezilla continues to display dates in mm/dd/yy despite being set to "use system defaults" date format.

[jeffg]

This is still a problem with the latest version (3.17.0). Running Windows 10 latest build with locale en_GB, but it is still displaying US date format. Time format (24h) is correct - if it was running with en_US locale I would expect the time format to be wrong as well (12h).

To the previous poster: en_UK is an invalid locale name: it is en_GB.

However en_GB is also not in the Languages list - the only English language variant is en_US. That is OK for the interface language, but not for use as the locale. My Language is set to "Default system language".

[JamesT]

I don't think this bug is being investigated anymore, Tim said on the forum the bug is "irreproducible" - ​https://forum.filezilla-project.org/viewtopic.php?p=140056#p140056

Sadly I can reproduce the bug every time I use FileZilla.

[Tim Kosse]

Starting with a fresh Windows installation, please describe all steps necessary to reproduce this issue.

[JamesT]

Steps required as follows.

• Install a fresh copy of Windows 10 Pro x64. At the first Windows Setup dialog box, set Language to English (United Kingdom), set Time to English (United Kingdom) and set Keyboard to United Kingdom.
• Install FileZilla 64-bit.
• Open FileZilla and observe that file date format is mm/dd/yy.
• Open File Explorer and observe that file date format is dd/mm/yyyy.

[Tim Kosse]

Cannot reproduce. Using the steps you described, the date/time is displayed identical in Explorer and FileZilla, both use the UK format.

[jeffg]

Well, you must be unique, because it doesn't work for anyone else - we can't all be doing something wrong. I am using Windows 10 Home 64 bit (not Professional) but it seems to be the same for Pro users.

Possibly the version you installed is not the same as the one that is available in the United Kingdom. Have you installed the "English (United Kingdom)" language pack? This link seems to concern a similar date format problem: ​http://forums.windowscentral.com/windows-10/375996-windows-10-has-turned-my-british-date-format-excel-into-american-date-format-how-can-i-get-turn-back.html

[JamesT]

codequid, could you perhaps try obtaining a Windows 10 iso via the Microsoft website at ​https://www.microsoft.com/en-gb/software-download/windows10 ? When downloading, set the Media Creation Tool to download an iso with Language: English (United Kingdom), Edition: Windows 10, Architecture: 64-bit. It will install without a key in trial mode.

I'm sure if you install this version in a real or virtual machine with the steps I outlined, that you will experience the bug we are all experiencing.

[Tim Kosse]

Something really strange is going on. The problem isn't the British English language per se, it's the absence of US English in presence of any other English language flavo(u)r.

[Gary]

Good spotting codesquid. That does correlate with the difference between my work and home machine. They are a very similar setup (both win10 now) but work does have US English installed, and doesn't have the bug.

[Tim Kosse]

Please try the most recent nightly build from ​http://filezilla-project.org/nightly.php

[Gary]

My dates are correct with default settings on that build.

[JamesT]

Same here, the nightly build fixes the bug for me.

[jeffg]

Which do I need: i686-w64-mingw32 or x86_64-w64-mingw32?

[ajtruckle]

I have this issue and I am using the latest build of the software. Help. :)