You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
macOS has one strange feature when creating files. If you create files with Russian characters "ё" and "й" from the system, these characters are written as characters with diacritical marks. When displayed in Aseprite, the diacritical character cannot be displayed, forcing the entire block of text to use an antialiased font for replacement.
As a quick solution, I drew these diacritics (Unicode U+0308 ̈ COMBINING DIAERESIS and Unicode ̆ COMBINING BREVE) onto the font so that the text doesn't break instead, but just displays one extra pixel for the text.
new aseprite_font
changed glyphs only
Changed symbols located at (x, y): (67, 507) and (89, 507)
Example:
I can also notice that when typing text inside the application, the characters are printed normally, without diacritical marks
The better solution
A better solution would be some mechanism that allows diacritics to be displayed on symbol and not after them by defining a negative glyph width. Alternatively, since all diacritics would appear as one or zero pixels on the font, a mechanism could be made that would simply skip displaying such characters without causing the smooth font to be displayed. Then it would be helpful to see a way to make the glyph image with 0 pixels wide so that it just doesn't show up and doesn't affect the text in any way. For now, in the edited font, I'm using the minimum allowable width of 1 pixel.
And here also a copyable examples of this symbols:
Diacritics: ё, й
Normal: ё, й
Aseprite and System version
Aseprite version: Steam Aseprite 1.3.6 (arm and intel both)
System: macOS Monterey and newer
The text was updated successfully, but these errors were encountered:
Hi @Catalyst-42 thanks for reporting. The rendering issue is a known issue with our sprite sheet/bitmap fonts format. Didn't know that macOS does an Unicode NFD (Normalization Form Canonical Decomposition) when saving files.
I'm not sure if there is a bitmap font format that supports combining chars, but if it does, we should adopt that format.
Mean while I'll add the proposed fixes in the font 👍
The problem
macOS has one strange feature when creating files. If you create files with Russian characters "ё" and "й" from the system, these characters are written as characters with diacritical marks. When displayed in Aseprite, the diacritical character cannot be displayed, forcing the entire block of text to use an antialiased font for replacement.
As a quick solution, I drew these diacritics (Unicode U+0308
̈
COMBINING DIAERESIS and Unicodĕ
COMBINING BREVE) onto the font so that the text doesn't break instead, but just displays one extra pixel for the text.Changed symbols located at (x, y): (67, 507) and (89, 507)
Example:
I can also notice that when typing text inside the application, the characters are printed normally, without diacritical marks
The better solution
A better solution would be some mechanism that allows diacritics to be displayed on symbol and not after them by defining a negative glyph width. Alternatively, since all diacritics would appear as one or zero pixels on the font, a mechanism could be made that would simply skip displaying such characters without causing the smooth font to be displayed. Then it would be helpful to see a way to make the glyph image with 0 pixels wide so that it just doesn't show up and doesn't affect the text in any way. For now, in the edited font, I'm using the minimum allowable width of 1 pixel.
And here also a copyable examples of this symbols:
Diacritics:
ё
,й
Normal:
ё
,й
Aseprite and System version
The text was updated successfully, but these errors were encountered: