I looked at what the gog api returns with curl (when in doubt, curl almost never lies) and I can confirm that the unicode replacement for some characters (notably &) doesn't come from my client, but directly from the gog api.
I'll fix it for a given set of characters by adding some substitution to manifest finalization. I suppose if I want to be gun-oh about it, I might just do a regex for all unicode characters and replace those that fall in the ascii realm (I guess its not too common that you'll see \uxxxx in a title and it meaning something other than unicode substitution). I'll see.
coffeecup: In addition, there is no overlap in file names concerning extras / installers :)
Its very unlikely, but given that certain games have installers in the extra and that file metadata appears to be managed by hand, duplicates would be possible.
So far, I encountered:
- Malformed xml when fetching file info
- Dangling files in the library that give a 404 or 403
- Duplicate filenames (for different files, not the same file under multiple languages)
Nothing surprises me anymore.
coffeecup: Anyway, it would be real neat but I can understand the concerns on your side.
I can't tell you with a straight face that I'll do it right away, but I think its a reasonable request.
I can't give you a firm timeline (its a nice feature, though not what I would consider a core one at least not if you view the backup more like a database and less like a gui that you will manually fiddle in... in my case, I'm doing my backup in an s3 store and then will implement a dashboard to access my games so this is very much my approach), but I'll find time for it.
Timboli: Though your
owned-games command does return the Title and Slug. Something
coffeecup may not realize, and which my GUI uses.
Oh yes. I'm just not using it in the manifest right now. His request is definitely not outlandish to implement.
Otherwise, given his reference to lgogdownloader, I strongly suspect that like me, he's on Linux.