Matmaus

It does look more complex :D but I like it. Actually, I am even thinking about extending your idea and completely moving to YAML. It would really simplify the code....

Thanks for the idea. I have created a different PR https://github.com/Matmaus/LnkParse3/pull/32 where I changed priting to a modified YAML. As this PR is no more relevant I am closing it.

Hi, [this](https://www.virustotal.com/gui/file/0482ccfefb4ff006ed1ab86fb2fec2cb6107d844e617ed73d023060d9872f119) sample is raising the same exception. Maybe it could help.

If I may, I would suggest to always return either `data` (dictionary object) or event better `document` (`OneDocument` object). Then any user can easily convert it either into JSON (`document.get_json()`)...

Hi, based on [documentation](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-shllink/16cb4ca1-9339-4d0c-a68d-bf1d6cc0f943) and on my quick dive into this problem I would suggest to use LinkInfo > The LinkInfo structure specifies information necessary to resolve a link target...

Hi, I check file from the first ZIP and I think the parsing is correct. You are right that Unicode strings are stored in UTF-16 but in this case LinkInfo...

Hi, sorry for the longer inactivity. 1) You have actually found the correct codepage - UTF-8. It works for file in the first ZIP. I can add UTF-8 encding as...