Announcement

Collapse
No announcement yet.

Bug in 2018 Ultimeat: External Editor Fontview not working

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug in 2018 Ultimeat: External Editor Fontview not working

    The windows font viewer worked in the previous version but no longer works in 2018 (I use ultimate)
    I have added the windows font viewer from C:\Windows\System32\fontview.exe as an external editor
    In 2018 it no longer loads the font and returns an error. This happens on any font and the fonts are valid and viewable in other viewers and in the windows font viewer when invoked from Windows Explorer
    ---------------------------
    Windows Font Viewer
    ---------------------------
    The requested file "E:\My Documents\My Gifts\Ventography_Personal_Use_Only910.ttf" is not a valid font file.
    ---------------------------
    OK
    ---------------------------

  • #2
    I do see this error in AC Pro 8, AC Ulti 10 and in AC Ulti 11. Did you use a batch or whatever to start fontview.exe in your previous versions?

    [edit]
    This one is really crazy. The command line

    Code:
    >"C:\Windows\System32\fontview.exe" "C:\Users\Emil\Desktop\New Folder\ahronbd.ttf"
    shows the error, but

    Code:
    >"C:\Windows\System32\fontview.exe" C:\Users\Emil\Desktop\New Folder\ahronbd.ttf
    works well. Notice the double quotes and the space in the path!
    Afaik AC always does enclose parameters with double quotes.

    Last edited by Emil; 09-01-2017, 11:09 AM.

    Comment

    Working...
    X