Reply to thread

Message

<blockquote data-quote="uxDesign" data-source="post: 999753" data-attributes="member: 117312">Hi, I have a strange issue with fonts.xml. I recognized that the time was missing in the home screen and figured out that TitanLight22 cannot be displayed. Reason seems to be that the number of fonts that can be used is limited to 19 and TitanLight20 is my 19.How I found it out (always cleared the font cache):- change common.time.xml to use&nbsp; TitanLight20 -&gt; ok&nbsp;- change common.time.xml to use&nbsp; TitanLight20 with size 22 -&gt; ok - added a font (fontB22a) before TitanLight20 and used TitanLight20 -&gt; nok- used fontB22a -&gt; ok&nbsp;here is my fontB22a definition&lt;font&gt;&lt;name&gt;fontB22&lt;/name&gt;&nbsp;&lt;filename&gt;TitanLight&lt;/filename&gt;&lt;height&gt;22&lt;/height&gt;&lt;start&gt;0&lt;/start&gt;&lt;end&gt;1536&lt;/end&gt;&lt;bold&gt;yes&lt;/bold&gt;&lt;/font&gt;There are no errors concerning fonts in the logs. All fonts are created in the cache directory.&nbsp;Can anyone reproduce this bug? I have it on two machines first running 1.3.0 release an now updated to the latest Titan V1.3.1.286.&nbsp;Logs are attached.&nbsp;Regards,uxDesign</blockquote>

[QUOTE="uxDesign, post: 999753, member: 117312"] Hi, I have a strange issue with fonts.xml. I recognized that the time was missing in the home screen and figured out that TitanLight22 cannot be displayed. Reason seems to be that the number of fonts that can be used is limited to 19 and TitanLight20 is my 19. How I found it out (always cleared the font cache): - change common.time.xml to use TitanLight20 -> ok - change common.time.xml to use TitanLight20 with size 22 -> ok - added a font (fontB22a) before TitanLight20 and used TitanLight20 -> nok - used fontB22a -> ok here is my fontB22a definition <name>fontB22</name> <filename>TitanLight</filename> <height>22</height> <start>0</start> <end>1536</end> <bold>yes</bold> There are no errors concerning fonts in the logs. All fonts are created in the cache directory. Can anyone reproduce this bug? I have it on two machines first running 1.3.0 release an now updated to the latest Titan V1.3.1.286. Logs are attached. Regards, uxDesign [/QUOTE]

Verification