custom page icons b...
 
Notifications
Clear all

We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.

Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.

custom page icons broke with 3.22

5 Posts
2 Users
1 Reactions
102 Views
(@rtruss)
Estimable Member Registered
Joined: 6 years ago
Posts: 88
Topic starter  

Sadness, v 3.22 will not render the below icon/logo set i chose to use.

COMMENT=color:%White%,style:wb,rich-text:1,text:\fSegoe Fluent Icons\\fArial\ Support Information
the 'box or blank between \ \' may not have transfered over but it would look like this in v 3.21 (headset icon)
 
 

   
Quote
Topic Tags
(@rtruss)
Estimable Member Registered
Joined: 6 years ago
Posts: 88
Topic starter  

Posted by: @rtruss

Sadness, v 3.22 will not render the below icon/logo set i chose to use.

COMMENT=color:%White%,style:wb,rich-text:1,text:\fSegoe Fluent Icons\\fArial\ Support Information
the 'box or blank between \ \' may not have transfered over but it would look like this in v 3.21 (headset icon)
 
 

here is what it actually looks like.

 


   
ReplyQuote
(@rtruss)
Estimable Member Registered
Joined: 6 years ago
Posts: 88
Topic starter  

I think I figured out what is up, the new 3.22 does not seem to recognize any fonts/symbols that are classified as 'Private Use Area'. So that will help me fix things on my end, I like the 'private use area' items better though. 😉


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

I've never heard of Private Use Area.  I read the article at https://learn.microsoft.com/en-us/globalization/encoding/pua.   It seems to be a set of character locations that are "undefined" and a developer can put whatever they want in there. From DTI perspective, it's all just "font".

Try saving your ini file as UTF-8-BOM.  It might be getting the text encoding wrong. It might need UTF-16 even judging by the examples in the above page.


   
ReplyQuote
(@rtruss)
Estimable Member Registered
Joined: 6 years ago
Posts: 88
Topic starter  

@glenn THANKS !!!  UTF-8-BOM was the trick!


   
Glenn reacted
ReplyQuote
Glenn's Page