Created attachment 159320 [details]
Patch for fontconfig port
SymbolNeu installed by x11-fonts/croscorefonts-fonts-ttf has an encoding problem that causes wrong character mapping. The details are described in https://bugzilla.redhat.com/show_bug.cgi?id=923346. This font is registered by 30-metric-aliases.conf installed by x11-fonts/fontconfig as a Symbol family font.
SymbolNeu as "Symbol" font should be disabled unless the encoding issue is fixed in the upstream. The attached patch comments out the entries in 30-metric-aliases.conf. There is no negative impact because one of other fonts is used as Symbol if required.
I don't have a problem with the patch, but I can't seem to find a upstream bug to go with this? neither does the redhat bug talk about that. I would like to include a upstream bug link to the patch so we can use that to keep track of what upstream is doing.
Sounds reasonable, but the upstream is ChromeOS and I do not think they have a public bug tracker (right?). While ChromiumOS source tree is available, it does not include this font as far as I can check.
This problem is caused by lack of Unicode map in the font file and recent fontconfig does not support legacy non-Unicode maps like Adobe-Roman. Maybe this problem does not occur on ChromeOS.
Sorry for being unclear, I was thinking about fontconfig upstream.
Is this still relevant?
I should have to look before I post something.
390 <alias binding="same">
605 <alias binding="same">
It is done and could be closed.