View Single Post
Old 03-02-2020, 07:40 PM   #22
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,105
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by DiapDealer View Post
I'm betting the ones it doesn't work on have a username with a space in it. It doesn't seem to affect other programs configured for "Open With" for other filetypes, so I'm guessing it's something to do with how fontview.exe itself parses a path with a space in it when it's provided as an argument.

I'm not at my computer to test, but it's the only thing that makes sense to me. My work machine's username has a space in it (not my doing). Moving Sigil's scratch directory to a location with no spaces in the path (and/or using an alternate font tool with the default space-infested scratch directory) should quickly prove my theory.
I just spun up a new VM from template and created the user with a space in the name. Installed Sigil, attempted to open a font file and errored out. Give the man a virtual cigar! I think he's got the answer. Hmm... wrapping the open with string in "s?
DNSB is offline   Reply With Quote