Internal Associations don't work with extensions containing control characters
Posted: 2020-11-05, 09:29 UTC
Internal association does not work (file type icon is not applied and associated program does not start) if extension name part has present a control character like left-to-right mark.
For example, on one of my read-only drives I have many files in PDF format with extension ".pdf" (the LRM character is between "f" and trailing quote mark). If in internal Asscociations I add such a new extension, change file type icon and set a program to open it, the association is created, but in TC I see blank white icon and after pressing Enter on file with such extension I see Windows dialog which asks to chosse the program which I want to use to open that file.
Furthermore, internal association which uses masks/wildcards, like *.pdf* or *.pdf? is not applied for such files either.
The character itself is not a problem for opening a file in desired program, e.g. if from TC's command line to launch:
d:\progra~1\sandbo~1\start.exe %HOMEDRIVE%progra~1\adobe\acroba~1.0\Acrobat\Acrobat.exe /a zoom=100 "file.pdf"
Adobe Acrobat opens the "file.pdf" file fine.
(off top: an example with Sanboxie is used because here launching Acrobat this way helps to avoid known Acrobat's "Fatal Error Acrobat failed to load its Core DLL", maybe someopne will find this info helpful).
For example, on one of my read-only drives I have many files in PDF format with extension ".pdf" (the LRM character is between "f" and trailing quote mark). If in internal Asscociations I add such a new extension, change file type icon and set a program to open it, the association is created, but in TC I see blank white icon and after pressing Enter on file with such extension I see Windows dialog which asks to chosse the program which I want to use to open that file.
Furthermore, internal association which uses masks/wildcards, like *.pdf* or *.pdf? is not applied for such files either.
The character itself is not a problem for opening a file in desired program, e.g. if from TC's command line to launch:
d:\progra~1\sandbo~1\start.exe %HOMEDRIVE%progra~1\adobe\acroba~1.0\Acrobat\Acrobat.exe /a zoom=100 "file.pdf"
Adobe Acrobat opens the "file.pdf" file fine.
(off top: an example with Sanboxie is used because here launching Acrobat this way helps to avoid known Acrobat's "Fatal Error Acrobat failed to load its Core DLL", maybe someopne will find this info helpful).