I can't attach because Thunderbird coughs up an error message, possibly due to my having done the set PATH command, which did work this time.
Sincerely,
Matthew Marcus
> The issue with fonts with special characters in family name was fixed in
> Inkscape 0.92.2 (see bug #1508928), so this should not be an issue
> anymore.
>
>> inkscape Dies with voluminous error messages to the console
> (attached).
>
> Is this the full output? It seems therem ight be missing something from the start (which could be due to the limited text buffer of the console window)
> You can write all console output to a file using
> "inkscape 1> output_stdout.txt 2> output_stderr.txt"
> Which will create two files in the current folder with the complete text content.
>
>> When I type 'path' after having done the set PATH,
>> it still shows many directories (attached).
>
> This means something went wrong. After executing "set
> PATH=C:\WINDOWS\system32;C:\WINDOWS" executing "path" will only show
> those two directories.
>
> You should try this part again, as you search path has *a lot* of
> entries and many of them could potentially cause issues. Anaconda3 is a
> likely candidate as it's built with MSYS2 (as is the newest Inkscape
> release) and could have installed conflicting library versions.
>
Dear Eduard. Regarding yours of Thu, 10 Aug 2017 17:03:35 -0000:
OK, here are Dropbox links: /www.dropbox. com/s/i0mryhl7a 1v29ck/ output_ stderr. txt?dl= 0 /www.dropbox. com/s/onu5qdhiw vbvww1/ output_ stdout. txt?dl= 0
https:/
https:/
I can't attach because Thunderbird coughs up an error message, possibly due to my having done the set PATH command, which did work this time.
Sincerely, \WINDOWS\ system32; C:\WINDOWS" executing "path" will only show
Matthew Marcus
> The issue with fonts with special characters in family name was fixed in
> Inkscape 0.92.2 (see bug #1508928), so this should not be an issue
> anymore.
>
>> inkscape Dies with voluminous error messages to the console
> (attached).
>
> Is this the full output? It seems therem ight be missing something from the start (which could be due to the limited text buffer of the console window)
> You can write all console output to a file using
> "inkscape 1> output_stdout.txt 2> output_stderr.txt"
> Which will create two files in the current folder with the complete text content.
>
>> When I type 'path' after having done the set PATH,
>> it still shows many directories (attached).
>
> This means something went wrong. After executing "set
> PATH=C:
> those two directories.
>
> You should try this part again, as you search path has *a lot* of
> entries and many of them could potentially cause issues. Anaconda3 is a
> likely candidate as it's built with MSYS2 (as is the newest Inkscape
> release) and could have installed conflicting library versions.
>