Model: font attributes

[jburel]

Review the font attributes
We currently have

• !fontStyle describing a mix of font style and font weight.
• fontFamily describing font.

The terms we have in fontFamily are probably wrong, but the miss-use is very common. In general use on the web they can either be a specific font family name (e.g.Times, or Ariel) or a generic family name. Thought in HTML/CSS you can list several in the attribute and they will be used in order if available on the system. This is nice and flexible but leads for complex string you need to parse. From the CSS/HTML spec suitable generic values are:

• serif
• sans-serif
• cursive
• fantasy
• monospace

I recommend we just need to have an enum of:

• serif
• sans-serif
• monospace

The value we have for fontStyle is not correct either. We are using it as a combination for style and weight.

From the CSS/HTML spec suitable values for style are:

• normal
• italic
• oblique

I had to check what the difference between italic and oblique was. Oblique is the normal letter shapes but slanted forward. Italic is also slanted forward but has different (normally more curved/flowing) letter shapes.

From the CSS/HTML spec suitable values for weight are:

• normal
• bold
• bolder
• lighter
• or a numeric value from (100,200,300,400,500,600,700,800,900)

I recommend we just need to have an attribute called perhaps fontStyleAndWeight using an enum of:

• normal
• italic
• bold
• bolditalic

---

Decision

• Merge fontStyle and fontWeight. Keep fontStyle. Update clients (#4469), schema and DB (see #4398)
• fontFamily will use enumeration cf. values above.
• Provide mapping for fontFamily (andrew)

[jburel]

Moved from sprint 2011-03-10 (7)

[jburel]

Moved from sprint 2011-03-24 (8)