Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.3.2
-
None
-
Linux pc 3.17.1-1-ARCH #1 SMP PREEMPT Wed Oct 15 15:04:35 CEST 2014 x86_64 GNU/Linux
-
824f01af8ffb39d94807c2b27d1259b9206b3014
Description
If the absolute path contains non-latin characters, QML FontLoader font is loaded, but can not be used for text rendering.
The status property is changed to FontLoader.Ready, the name property is correctly populated, but text rendering fails and is done using a fallback font.
A non-latin path, containing a qml and a ttf, where qml loads the ttf using a relative path: (source: 'myfont.ttf') also results in broken font loading.
Loading remote fonts urls works fine, even from non-latin urls, because the fonts are loaded in memory and the absolute path becomes something like ":qmemoryfonts/0".
A possible fix would be to load all fonts to memory, or to fix the non-utf paths somewhere.
I attached FC_DEBUG=4 logs.
Also I attached two test qml files (which could be alternatively downloaded from http://oserv.org/bugs/qml/fonts/), the font used is http://www.paratype.ru/uni/public/PTSans.zip
When those two qml files are placed in a non-latin path, font_remote.qml works fine while font_local.qml fails to use the font.