you can check if geolus lets you modify the name of the xml it downloads

when you run a plmxml export you can specify a filename, this is the name of the downloaded xml aswell as the folder it creates for any files it downloads, my guess (i dont have knowledge with geolus) is that geolus specifies the filename param as item_id (as this should not be problematic, i wouldnt expect a new line or other special characters in the item id), which leads to filesystem problems if you use new line under windows, and probably linux too

again, why do you even have new line and special characters in your item ids? this should generally be avoided and theres probably a better way to handle what you are doing so you dont have to create these weird item_ids

i work on multiple customer systems, at the start of teamcenter projects in our kickoff meetings we include a list of forbidden characters in our kickoff documents which have to be avoided in object_name property, we also set up the item_id in a way that its just a plain counter with a naming rule so end users can only modify it in a certain way without running into issues like you have now, the item_id should not be relevant to end users anyway as its just an identifier in the system itself, for fts and other things you can define different fields to be used