Comment # 8 on bug 1189267 from Steffen Winterfeldt

Not without maintaining an 'acceptable' alias list or something like that.

When I ran a quick check with the new font package fc-match returned:

"Source Sans Pro" -> "Source Sans 3"

but other variants were not mapped in any useful way. For example:

"Source Sans Pro Light" -> "Roboto"

So, IMHO this looks not the way to go.

If we were to implement something in check_font we'd have to have a list
of aliases we'd accept for a specific font; like,
"Source Sans 3" is ok for "Source Sans Pro" but "Roboto" not.

This can get out of hand quite easily and it seems better to me to just adapt
the css files.

In my opinion the best way to avoid all this would have been to simply create
new
packages for '3' and keep the 'pro' fonts as is. Especially as the point of the
font designer seems to be that the metrics differ from pro and the threat
is that there will be '4' etc in the future anyway.