Find does not support 4 bytes.
It can’t even show.
I am a Chinese.
Cjk fonts are difficult to find.
Some fonts don’t even have unicode numbers, which is more difficult to find.
How do characters without unicode numbers correspond to codes one by one?
Can we increase the support for 4 bytes in the future?
It is best to be able to find it by characters.
If you can’t do it.I hope I can find non-unicode encoded characters through Hexadecimal.
Example: 2EBF000
Find � in hexadecimal.
U+2EBF0 is the very first character in the CJK Unified Ideographs Extension I block.
FontCreator’s Find dialog can locate it: Enter: $2EBF0. If that isn’t working on your end, please let us know the exact steps you’re taking and what appears on-screen so we can reproduce the problem.
For glyphs that have no assigned Unicode code point, you can still search by their glyph name in the same dialog.
Glyph Properties Name is glyph01.Glyph Properties Code-points is null.Edit-Find is Could not find next occurrence of “$2EBF0”.character UTF-32LE Code is F0 EB 02 00.Support 4 bytes when searching.Non-unicode encoding is added to the Glyph Properties.
It looks like the glyph named glyph01 isn’t mapped to any Unicode code-point, which is why the Find dialog can’t locate U+2EBF0—it can only search glyphs that have a Unicode value assigned.
Could you send us the font file (or a small test sample) so we can see how that glyph is set up? With the file in hand we can confirm what’s going on and suggest the best way to map the character—or offer another workflow if the glyph is intentionally left unencoded.
Some characters in CJK Unified Ideographs Extension H。
FKPFEP+UCS_K_ExtHv1.ttf
I have no idea how to download it from there.
I sent an email to Erwin de Nissen via high-logic Forum,[email protected] this is not your email address,please reply.I will send you another email with the font as an attchment.
That “noreply” address isn’t monitored, so your message won’t reach me. I’ve just sent you a private message with instructions on how to share the font.
I found a network disk.
You can download it without logging in.
FKPFEP+UCS_K_ExtHv1.ttf for you.
If your research is successful, it means that a ttf file can hold all Unicode.
I’ve opened the font you sent. Only four glyphs are mapped to Unicode code-points:
- uniE967
- uniEA0B
- uniED5F
- uniEC50
The remaining 618 glyphs have no Unicode assignment, so FontCreator’s Find command can’t locate them by code-point. At the moment they’re effectively “orphaned” outlines that the software treats as unused.
If those unmapped glyphs represent real characters you want to access, you can map each glyph to its proper code-point (e.g., U+2EBF0 for your first Extension I character). Once mapped, Find will work.
I’m not to add unicode code.I want to know how to read non-unicode encoding.Glyph Properties adds a new function of non-unicode encoding.Find a new function to support non-unicode encoding.You don’t understand what I mean.Unicode only supports 65535.non-unicode encoding supports 4294967295.non-unicode encoding is used normally.This means that I can put all unicode characters into one font file.
Unicode isn’t capped at 65 535. That limit applied only to the old Basic Multilingual Plane (BMP). Modern Unicode has 17 planes—U+0000 to U+10FFFF—so a bit more than 1.1 million legal code-points.
U+2EBF0 (CJK Extension I) is already in Plane 2, so it’s a perfectly valid 4-byte Unicode value.
Only 2 bytes are supported.Only 65535 is supported in Fontcreator.non-unicode encoding supports 4294967295.
FontCreator has supported the full Unicode range up to U+10FFFF (over 1.1 million possible code-points) for more than 20 years.
You can try adding 70000 unicode characters and then output ttf.
Currently the OpenType specification allows up to 65K glyphs, but that might change very soon. However the number of characters is unlimited.
Here is a last resort font. It is only 944 bytes.
https://www.high-logic.com/fontcreator/demo/lare/LaRe.ttf
LaRe is an OpenType font with TrueType outlines. It contains two glyphs, the .notdef glyph and an empty glyph for the entire Unicode range (0x0000-0x10FFFF).
As I already told you, currently the OpenType specification allows up to 65535 glyphs, but the number of characters is unlimited.
Insert-Glyphs-65537，Only 1 Glyphs will be inserted.Unicdoe 65537 cannot output TTF..Does not support infinity at all.I know the reason why the whole program runs slowly.Programmers deliberately make a lot of restrictions.Obviously there are many system resources that can’t be used.This is just a font making software, not a resource-intensive 3D game,It shouldn’t be so slow.
If you insert $00-$10FFFF, it will get stuck.