Re: [PATCH 5/6] dwrite: Use MapCharacters for non-visual characters

[Nikolay Sivov]

On 05/26/2018 05:01 PM, Lucian Poston wrote:
> > What we need to figure
> > out here is which font is picked in NO_VISUAL case, does it change with
> > range locale,
> > or custom collection. Then we can either hardcode it here, or add
> > corresponding char ranges.
>
> Going from memory, it was tahoma in win 10 (without custom collection), but I
> suspect that comes from the system font collection or system fontfallback
> object.
>
> I don't know if you'd want to hardcode it here. The fontfallback allows you
> define a mapping between char ranges and font, so the system's fontfallback
> would seem like the appropriate place for that.

Depends on how it works, but yes, doing that in fallback object is 
preferable.