Win 10 Font Install issue (0.92.3 (2405546, 2018-03-11))

This has been fixed for 0.92.x on the Feb 26 2019 (and also 1.0alpha)

For text use right now (i.e. this month) its probably best to stay in 0.92.x (0.92.4 preferred)

Is 0.92.4 out officially, or still a beta build?

On Sun, Apr 14, 2019, 07:50 Nathan Lee <email address hidden> wrote:

> This has been fixed for 0.92.x on the Feb 26 2019 (and also 1.0alpha)
>
> For text use right now (i.e. this month) its probably best to stay in
> 0.92.x (0.92.4 preferred)
>
> ** Tags added: bug-migration
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1810352
>
> Title:
> Win 10 Font Install issue (0.92.3 (2405546, 2018-03-11))
>
> Status in Inkscape:
> New
>
> Bug description:
> Windows 10 changed where new fonts are installed, to
> C:\Users\[Username]\AppData\Local\Microsoft\Windows\Fonts
> Inkscape doesn't look in this folder for fonts, meaning that you have to
> manually put fonts into the old C:\Users\Windows\Fonts folder in order for
> them to appear.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/inkscape/+bug/1810352/+subscriptions
>

Closing because fix has been committed.

0.92.4 is out officially and is stable. Unfortunately, the commit I mentioned isn't released yet.

In the meantime, I think the workaround is to "install font for all users" or "install as admin".

Here is the issue on gitlab which discusses this problem and the workaround https://gitlab.com/inkscape/inkscape/issues/50 (Inkscape's been migrating bugs to gitlab so this got the attention).

Closed by: https://gitlab.com/nathanal