The target file can be opened directly. But can’t open it from .lnk.
Error: A problem occurred loading file ‘D:\?üD?.txt’ :
The System Cannot Find the File Specified.
Thus.
It is possible for you to email the lnk file to ‘support@sweetscape.com’? lnk files can encode file names in multiple ways and we’d like to see how the file name is encoded in this file. Cheers!
Graeme
SweetScape Software
Here it is.
I think maybe it is missed a byte when the name is converted ASNI (GBK?) to UTF-8.
How was this LNK file generated? LNK files can contain two paths: an 8-bit character string and a 16-bit character string. The spec seems to indicate the 8-bit character string should always be encoded as ANSI and the 16-bit is encoded as UTF-16. The file you sent does not have a 16-bit character string but appears to have a UTF-8 character string stored where ANSI data is expected. If you right-click on the file in Windows Explorer and choose ‘Create shortcut’, a LNK file is generated which works correctly with the 16-bit string. It looks like when the LNK file was generated the 16-bit string was missed. We could add some code in the future to try to detect if an UTF-8 string was inserted by mistake but we wouldn’t want to mess up other LNK files.
Graeme
SweetScape Software
By this way. I am not sure if it’s in Windows Explorer. I just go to the file’s path, then “create shortcut” or “send to desktop” by context menu.They are same errors.
We can put in a extra check in 010 Editor to see if the file exists using either the ANSI or UTF-8 encoding and this should allow your file to work. We will try to get this in our next version, which we hope to have out in about 3 months. Cheers!
Graeme
SweetScape Software
I made a mistake earlier. The string ‘D:?üD?.txt’ is not just a utf-8 encoding of the chinese characters. Instead it appears to be garbled and we cannot figure out what encoding was used to make this string. Can you please verify which program created the LNK file as the LNK file appears to be generated incorrectly? It looks like the LNK file was made in something other than Windows Explorer.
Graeme
SweetScape Software
Go to the path where the file in, and create it by context menu on Windows 10 x64.
Not use other 3rd-party way.
The correct name is “更新”. I had uploaded it with the .lnk in the zip file.
Blockquote
D:\¸üÐÂ.txt
I am sorry. I copied it to an ANSI text file. It’s showed ? character instead of some characters which it is not supported. So, this is really the bad one.
If I change the target file name to “¸üД, then it can be opened from .lnk with 010 editor. I don’t know the garbled is which encode, try GBK or GB18030, it is also garbled.
I have known it.
The hex of “更新” is “B8 FC D0 C2” in GBK or GB18030.
It is showed “¸üД in the right ASCII characters.
010 edtior doesn’t convert the ASCII characters. Then the name is garbled.
We figured out that the ‘D:\¸üÐÂ.txt’ filename is just a GB18030 encoding of the file. Windows 10 appears to use the system locale when creating the Lnk file but then never stores which locale was used when creating the file name inside the Lnk file. Windows 11 seems to fix this by just writing a Unicode file name. The Lnk file also contains RELATIVE_PATH and WORKING_DIR strings which we can use to form the file name and these appear to be Unicode even on Windows 10. There are issues where this is not consistent either, so we’ll probably have to check for the regular link info and relative path links. We should be able to get this check into our next version, which we’re hoping to have out in 2 or 3 months. Cheers!
Graeme
SweetScape Software