Henri Le Forestier
My feedback
1 result found
-
163 votes
The team plans to push the fix from the Beta build into the main one in first week of January — hooray!
The current workaround in 29.1 is to disable Missing Glyph Protection option in Preferences > Type.
An error occurred while saving the comment An error occurred while saving the comment Henri Le Forestier commentedJust to clarify, the workaround was found by Adobe, I was just upping it as I saw many of you blocked on the issue (and the workaround was hidden by many comments)
Happy it helped :)An error occurred while saving the comment Henri Le Forestier commentedA shame that this isn't fixed yet. FYI if you're still struggling, the workaround:
In the Preferences menu, Type > Enable Missing Glyph Protection -> uncheck the boxHenri Le Forestier supported this idea ·An error occurred while saving the comment Henri Le Forestier commentedWhenever I have a text zone with ANY font, if I input new text, it will ALWAYS output the new text in Arial Bold, regardless of the original text font (whether it's Arial Regular, or some custom font).
This is more than frustrating, it's kind of a blocking issue, since I cannot edit any text without having to manually set again the font for the text zone.
To reproduce:
- Create a text zone, type some text
- Set the text zone to be another font than Arial Bold (you can choose Times New Roman or Futura)
- Edit the text, the new text will be Arial BoldExpected:
New text should be the same properties as the rest of the text zoneIllustrator 29.1 (64-bit) Windows 11
I have a revolutionary idea for that: why don't you test basic features before releasing?