Currently if a client creates a project in SDL Managed Translation and wants to upload two huge MS Office files in a ZIP file from a MacIntosh computer, the client sees these files in his ZIP file:

/huge_Word_file.docx
/huge_Powerpoint_file.pptx

What SDL Managed Translation receives is this:

/huge_Word_file.docx
/huge_Powerpoint_file.pptx
/__MACOSX/huge_Word_file.docx
/__MACOSX/huge_Powerpoint_file.pptx

Uploading MS Office files without zipping them can be a bad idea, since depending on the connection quality part of big file might get lost.

What SDL Managed Translation should do ideally is the following:

It should simply ignore the MacIntosh resource fork files and either delete them or convert them into reference files, since if the Preprocessing workflow step picks these MacIntosh resource fork files up, the module will not able to handle them and through an error.

Can SDL Managed Translation be made so robust to handle Macintosh ZIP files in an efficient way?