Single Versus Multiple Tables
One more point is worth addressing here. If you need to perform several different mappings on Unicode characters, do you want to use a completely separate table for each mapping or use one big table for all of them?
It's obviously tough to generalize, but sometimes a big unified table will certainly save space and time relative to a bunch of smaller, more specific tables. The most common case is dealing with the Unicode character properties: Should there be a separate table for each property, or a huge table for all of them? The answer is that you can cram most of the Unicode character properties into a single table. The majority of the Unicode properties for a single character can be jammed into a single 32-bit ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access