Translating things:
ME: "Hey dev, can you send me a xml file of strings to translate so you can impleme..."
DEV: "yea yea tomorrow"

He sent a .docx file.

i'm crying

Oh boy, doesnt he have at least Excel?
Also welcome to DevRant

@legionfrontier thanks! what a cool place hahahha

Technically docx is at least partly xml.

Its a ziped directory containing many files but the once containing the text is xml files ;)

@Voxera it's a different thing when you requested a certain file but recieved another, but i see your point of view

@Roxas22 We often get screenshots and other images pasted in word. So I do feel with you.

We also do get some interesting file formats when customers are sending data for import when moving to one of our systems, and specifying xml there does often not help either, even when they actually send as xml.

Specifying xml is actually not more precise than specifying text or binary since its just markup.

Without a defined structure it can be a complete mess and still be a valid xml file.

@Voxera i completely agree! often i don't care about what the dev have to do whit the translated file, but i think that a rubbish file for me can be a problem to the dev, i though

One time a client asked me to export all text from a ui into a text document. Later they came back "we got the file translated to German" please import it back in. Well I didn't realise that is what they wanted the export for. There were no ids and many bits of text on multiple lines so it was very difficult and problematic to import.

Both have x in the name, I don't see the problem here

Funfact. Docx is basically encapsulated xml
In some cases it also can be parsed as such. It gets preeeeetty fcked up, when binary stuff as images get involved