View Single Post
Old 03-03-2020, 03:10 AM   #24
un_pogaz
Chalut o/
un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.un_pogaz understands the importance of being earnest.
 
un_pogaz's Avatar
 
Posts: 439
Karma: 145424
Join Date: Dec 2017
Device: Kobo
Quote:
Originally Posted by DiapDealer View Post
Verified. Fontview.exe doesn't like a path argument enclosed in quotes whether the path has a space in it or not. I don't think I've ever run into a windows program that wouldn't accept a path argument enclosed in quotes before (provided a path to a file to open can be passed in as an argument in the first place). Weird. And the Windows Open With code uses methods that automatically build the parameter string and add quotes wherever deemed necessary. Works with just about every other program I've ever tried it with except fontview.exe ... spaces or no spaces. Have I said "weird" yet?
What??
testing
Yep
I confirm. fontview.exe does't accept quotation marks as command line arguments.
Dammit, even the basic Drag and Drop (if there is a space in the name) doesn't work!
(probably a legacy of very old Windows version)

I don't know if you could do anything to make sure fontview.exe works (although it's really useful).
But if not... too bad (and damned Microsoft)

Last edited by un_pogaz; 03-03-2020 at 03:15 AM.
un_pogaz is offline   Reply With Quote