Search found 128 matches
- Sat Jan 20, 2018 3:03 pm
- Forum: FontCreator - Discussion
- Topic: Glyph Names for export
- Replies: 2
- Views: 3784
Glyph Names for export
In the Font Export Settings dialog box, on the TrueType/OpenType tab, if the " Glyph Names " is set to " Regenerate for release ", are the mappings in the FontCreator file glyphnames.dat used? Or is there some other approach / algorithm that is used on export? I'm thinking that g...
- Sat Jan 20, 2018 11:53 am
- Forum: MainType - Support
- Topic: Filter fonts by Code-Point or Block?
- Replies: 3
- Views: 3516
Re: Filter fonts by Code-Point or Block?
Both suggestions are very helpful and this is workable! I can imagine a display - a column in the main font View List - that shows a "Block Coverage" display, maybe color-coded by the % coverage of the block. With 280 blocks, that may be unwieldy ... maybe you get to select which blocks ar...
- Sat Jan 20, 2018 1:16 am
- Forum: MainType - Support
- Topic: Filter fonts by Code-Point or Block?
- Replies: 3
- Views: 3516
Filter fonts by Code-Point or Block?
Is there a way in MainType (ver 8.0) to show all or filter fonts that have a given code-point mapped? Or maybe that have code-point in a given block??
-Clint Goss
-Clint Goss
- Sun Jan 14, 2018 7:50 pm
- Forum: FontCreator - Bug Reports
- Topic: [FIXED] Bug recognizing non-assigned code points
- Replies: 3
- Views: 4346
Re: Bug recognizing non-assigned code points
Thanks Erwin! This is, of course, a pretty low-priority issue, but one that might cause heartburn here and there for a few folks. I believe that those are the only issues of this type, because with those corrections, the number of total defined Unicode 10.0 code points that are not private use and n...
- Sun Jan 14, 2018 6:27 pm
- Forum: FontCreator - Bug Reports
- Topic: [FIXED] Bug recognizing non-assigned code points
- Replies: 3
- Views: 4346
[FIXED] Bug recognizing non-assigned code points
I think this is a bug, although I'm pretty new to this stuff ... I'm using FC Pro 11.0.0.2408, which seems to be the latest, on Win7x64. It appears that a number of the Unicode 10.0.0 blocks have non-assigned characters which are not recognized as such by FCP. In particular (this is cut-pasted from ...
- Tue Nov 07, 2017 12:31 pm
- Forum: FontCreator - Support
- Topic: Hiragana / Katakana not recognized
- Replies: 8
- Views: 4295
Re: Hiragana / Katakana not recognized
Thanks for the support, All! I think the real answer is that it's not the fonts, it's my (ill-)chosen App for trying to author a book - Microsoft Word. Yes, there were some issues in my font (thanks to Bhikkhu for taking the time to correct those!) But it is the *breathtakingly arbitrary* way that W...
- Mon Nov 06, 2017 4:58 pm
- Forum: FontCreator - Support
- Topic: Hiragana / Katakana not recognized
- Replies: 8
- Views: 4295
Re: Hiragana / Katakana not recognized
Thanks Erwin ... glad to know it wasn't something silly, but sad to know it still unsolved. I have done a trial by setting the checkbox on "JIS/Japan (932)" and turning off Auto Update on export, but no joy. I'm guessing that is what you meant by "manually set specific code page chara...
- Mon Nov 06, 2017 2:38 pm
- Forum: FontCreator - Support
- Topic: Hiragana / Katakana not recognized
- Replies: 8
- Views: 4295
Hiragana / Katakana not recognized
Hello - I've been at this for days, and hoping more experienced eyes can easily diagnose. Using FontCreator 11.0 Professional. Added Hiragana & Katakana Unicode blocks to a font. However, Word and Corel refuse to use those code-points from my font, falling back to a default font for those charac...