That is just how OpenType layout features work. They are bound to a script.
I strongly recommend to move forward and correct the codeponts to the actual Unicode values.
Search found 6068 matches
- Fri Feb 12, 2016 9:04 am
- Forum: FontCreator - Support
- Topic: OpenType features with chars from different Unicode blocks
- Replies: 2
- Views: 2379
- Wed Feb 10, 2016 4:59 pm
- Forum: MainType - Support
- Topic: Stuck at Loading... how to bail out?
- Replies: 2
- Views: 2901
Re: Stuck at Loading... how to bail out?
You can remove the folder through the font folder dialog.
Is it a large folder or slow drive?
Is it a large folder or slow drive?
- Wed Feb 10, 2016 1:48 pm
- Forum: FontCreator - Bug Reports
- Topic: [FIXED] Minor error in Welcome screen
- Replies: 1
- Views: 2992
Re: Minor error
Thank you for reporting this issue!
- Wed Feb 10, 2016 8:57 am
- Forum: MainType - Bug Reports
- Topic: Font Tags whose names start with "-" (hyphen) don't work with Tag Search
- Replies: 2
- Views: 9949
Re: Font Tags whose names start with "-" (hyphen) don't work with Tag Search
Your findings are indeed correct.
The minus sign causes the problem, as that character is used internally. Just start with any other character and you're good to go!
The next upcoming major release will not accept tag names starting with a "-".
The minus sign causes the problem, as that character is used internally. Just start with any other character and you're good to go!
The next upcoming major release will not accept tag names starting with a "-".
- Tue Feb 09, 2016 6:27 pm
- Forum: FontCreator - Support
- Topic: OTF files associated with FC
- Replies: 6
- Views: 3647
Re: OTF files associated with FC
This is not how it is supposed to work. I'm sorry.
- Tue Feb 09, 2016 5:39 pm
- Forum: FontCreator - Support
- Topic: OTF files associated with FC
- Replies: 6
- Views: 3647
Re: OTF files associated with FC
We've tested this new functionality with both Windows 7 and Windows 10, and both didn't automatically assign FontCreator as the default program.
It is possible Windows did assign it in case no other software was assigned to that file extension, but I can't verify this.
It is possible Windows did assign it in case no other software was assigned to that file extension, but I can't verify this.
- Tue Feb 09, 2016 2:57 pm
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
The latest version (9.1.0.1991) did solve the problem.
Better avoid using the older versions!
Better avoid using the older versions!
- Tue Feb 09, 2016 2:20 pm
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
I really want to find the cause of this problem...
- Tue Feb 09, 2016 2:13 pm
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
This version also seems to fail on kerning in WinAmp. At least on my old Win XP.
- Tue Feb 09, 2016 1:57 pm
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
Please can you also send me a font file (exported through 1950) so I can see how that one works?
- Tue Feb 09, 2016 12:36 pm
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
Can you send the font and/or the font project to me?
- Tue Feb 09, 2016 11:49 am
- Forum: FontCreator - Bug Reports
- Topic: [CLOSED] Kerning Pairs are lost after saving closing and reopening
- Replies: 5
- Views: 4499
Re: Kerning Pairs are lost after saving closing and reopening
Also be ware you should no longer change a glyph's side bearings as soon as you start with the kerning. If you do change for example the right side bearing of the "f" all kerning pairs that start with the "f" will have to be corrected.
- Tue Feb 09, 2016 11:40 am
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
I've just found the cause of the problem.
You accidentally enabled "Ignore Base Glyphs". With this option all glyphs with GlyphType set to Simple are skipped. Obviously most/all of your kerning glyphs are simple.
So uncheck that box, and all should work again!
You accidentally enabled "Ignore Base Glyphs". With this option all glyphs with GlyphType set to Simple are skipped. Obviously most/all of your kerning glyphs are simple.
So uncheck that box, and all should work again!
- Tue Feb 09, 2016 11:04 am
- Forum: FontCreator - Bug Reports
- Topic: [CLOSED] Kerning Pairs are lost after saving closing and reopening
- Replies: 5
- Views: 4499
Re: Kerning Pairs are lost after saving closing and reopening
I've just:
- Opened the project
- Went to the fr kerning pair and set XAdvance to 140.
- Pressed the OK button.
- Saved the project.
- Opened it again.
- And see the value is 140.
So it works just fine here.
- Opened the project
- Went to the fr kerning pair and set XAdvance to 140.
- Pressed the OK button.
- Saved the project.
- Opened it again.
- And see the value is 140.
So it works just fine here.
- Tue Feb 09, 2016 10:26 am
- Forum: FontCreator - Support
- Topic: Winamp Does not kern using update 1970.
- Replies: 16
- Views: 8177
Re: Winamp Does not kern using update 1970.
We've just released another update, do let us know if that solves the problem.