Planned changes to Symbol enum & font

Some updates/fixes coming to the Symbol enum and font. Primary goal here is to cut down on repetitive icons and icons without glyphs.

• Several icons have incorrect glyphs, will be corrected

• Symbols in the enum:

  • Favorite will removed. Star serves the same purpose
  • CodeFilled will be removed
  • Add CodeHTML value, code will map to braces (‘{ }’) and CodeHTML will map to (‘</>’)
  • MoreHorizontal will be removed in favor of just More.
  • Left, Down, and Right will be added (Up already exists), these icons are arrows pointing in their respective direction
  • Setting will be removed, use Settings (singular vs. plural)

• Symbols marked as Obsolete Several symbols are marked as Obsolete as they didn’t have glyphs from Fluent UI System icons

Symbols in green will be added to the font & have Obsolete removed. Symbols in yellow and grey still don’t exist, but could probably be made manually in inkscape (or any vector editing app, mostly reusing the existing icons), need to figure out if the system that’s used to build the font would support this. Note that this is only an option at this point. Placeholder will be removed

• Various Filled variants of icons will be removed. These all pertain to icons that are mostly lines, like Chevrons, arrows, etc. These aren’t truly filled anyway. The normal versions will remain, though

I believe most of these are placed in a special area in the font specifically for FluentAvalonia. If so, they will likely be removed from the font too.

Within the actual font, various icons that didn’t previously have glyphs, now do and will be added to the font

[robloo]

@amwx

I manually added an entry in the json file with the destination unicode point set to 0000 and it crashes on line 174 in FluentAvalonia.RebuildMappings (“invalid symbol enum icon detected”).

I fixed this issue. Basically, this is the first time the FluentAvalonia mappings have been re-built with existing, custom UnicodePoints already assigned. So it was missing the logic needed to detect the max UnicodePoint already used and then start from there (not start from 0xF8000).

Also keep in mind the rebuild process will re-sort the mappings by destination icon name. This is to keep things stable but in practice it means any mappings you add at the end will be moved once a name is assigned.

Finally, I updated the project to .NET 7.0 so you might need to install the new SDK.

[robloo]

@amwx FluentAvalonia.json is ready for your changes now. Everything also should be able to build offline using local SVG files in the repo itself. This hopefully means everything is stable going forward and it will always build as it does now.

All icon mappings should be fixed (the 3 base windows symbol font mappings) then I copied those fixes into FluentAvalonia.json. So the “icons needing update” should be done already. The only thing you have to do is delete the FA-specific icons you no longer want in the font. ONLY delete the ones in the FA-specific Unicode range above 0xF8000 though. Any changes you make elsewhere will be overwritten the next time the mapping is rebuilt from the base SegoeFluent information.

Avalonia itself has issues so the mappings editor doesn’t always display correctly. There are several ListBox issues I noticed and also an issue with container recycling or images causing the display of incorrect glyphs even though the view model and mappings are correct. So be careful there – it might be the data is correct just Avalonia is messing it up in the UI.