Windows, adding a .jpg picture in Nuxeo Drive folder does not create a Picture doc. type

[Environement set to 5.7 because I did not test it on 5.6]

Windows 7, runnning in a VM machine on Mac.

Regular, fresh 5.7 Snapshot running (nuxeo-cap-5.7-I20130603_0116-tomcat) on the same VM (I mean I connect at localhost:8080), with Nuxeo Drive MP package. No customized application (no Studio project bound, no custom bundle, .... Just 57 + Drive)

Quit previous Drive that was running, delete the .nuxeo-drive and Nuxeo Drive folders.

Start Drive, connect to localhost:8080 as Administraotr.
Create a workspace ("ws"), a folder ("f") in this workspace.
Activate synchronization for the workspace.
In Nuxeo Drive, add a .jpg picture to the "f" folder

=> The picture is added, but the document is a "File", as confirmed with the XML export:

<document repository="default" id="e02bb746-5ed3-40c3-b647-cd981e1475a9">
<system>
<type>File</type>
<path>default-domain/workspaces/ws/f/bag-1.jpg</path>
[...]

=> On Mac, no problemo, a document of type "Picture" is created

Why is it "Major"? Because it breaks an application: A event handler is fired for "on document created" of documents of type "Picture" or "Video". It is nevere triggered when a new image is added to the system by drag-drop to the Nuxeo Drive folder on Windows.
Mor generally speaking, it will breaks anything that filters the run/display of an object depending on the "Picture" type.

Another big issue, side-effect, is that, because it is created as a "File", it missed the "Picture" default facets and behaviors.

When digging into it, it looks like the extension sent by Windows is .JPG, not .jpg
=> There is probably a case-sensitive test in Nuxeo to get the mime-type of the file.
(note: hope it does not apply to TXT )
NOTE #2: I tested on...
gif => OK, "Picture" created
png => not OK, "File" created