On Mon, Nov 15, 2010 at 4:04 PM, David Marshall
<email address hidden> wrote:
> But from experience we can say that this confuses people greatly. They
> installed a Medium weight, so expect to see a FamilyName Medium in their
> font list - most don't even think to look for it as a "Light Bold".
>
> We have in the past engineered duplicate fonts with different names at
> the request of clients, so they get both a Medium and a Light Bold, but
> this then creates problems for the preferred naming.
It's probably easier for the users to find Medium in a family Ubuntu
Medium if the app is limited to legacy names (4 variants).
Applications that can handle preferred family names and weights should
use Regular when Light is bolded, and Bold when Regular or Medium are
bolded. So my earlier suggestion of having Medium as the "Light Bold"
would be inconsistent with that.
On the other hand having a Light and a Medium legacy family names,
would mean the user would get faux bold in apps only supporting legacy
names.
Which is why I think having all apps handling preferred names is the
way to go. But I guess it is why one would want to jump through loops
with fontconfig.
On Mon, Nov 15, 2010 at 4:04 PM, David Marshall
<email address hidden> wrote:
> But from experience we can say that this confuses people greatly. They
> installed a Medium weight, so expect to see a FamilyName Medium in their
> font list - most don't even think to look for it as a "Light Bold".
>
> We have in the past engineered duplicate fonts with different names at
> the request of clients, so they get both a Medium and a Light Bold, but
> this then creates problems for the preferred naming.
It's probably easier for the users to find Medium in a family Ubuntu
Medium if the app is limited to legacy names (4 variants).
Applications that can handle preferred family names and weights should
use Regular when Light is bolded, and Bold when Regular or Medium are
bolded. So my earlier suggestion of having Medium as the "Light Bold"
would be inconsistent with that.
On the other hand having a Light and a Medium legacy family names,
would mean the user would get faux bold in apps only supporting legacy
names.
Which is why I think having all apps handling preferred names is the
way to go. But I guess it is why one would want to jump through loops
with fontconfig.