Re: [PATCH v2 0/4] MR11035: gdi32/uniscribe: Eagerly cache cmap tables for a font.

[Nikolay Sivov (＠nsivov)]

On Tue Jun  2 19:01:30 2026 +0000, Nikolay Sivov wrote:
> Ok, yes, in this case it's not much worse to keep cmap too. But at the
> same time we already have 'page' array which is exactly the same -
> lazily allocated copy of a cmap. Generally I think it's easy to keep
> cmap in its original format, because it's fast to lookup already.
> Regarding keeping multiple cmap tables, why do we need this? I don't think you are supposed to navigate multiple tables when you map characters. I'm pretty sure harfbuzz for instance does not do that, and our dwrite doesn't either, see dwrite_cmap_init().

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/11035#note_142029