Jacques Le Roux wrote:
In UI, we begin to hit the Pareto principle
http://en.wikipedia.org/wiki/Pareto_principle
This is a good and a bad news. It means we achieved most and to achieve
the rest it will cost us (actually in our case, I'm much more confident
because we actually hitted Pareto wall earlier :o)
[citation needed]
Typography
Typography depends on languages. For instance in French we put a space
after colons, there are other cases of course. So punctuation should be
always part of labels.
HTML
We already discussed about not putting any HTML tags in labels. Actually
we should at least not allow any < and & which will not be correctly
rendered (http://www.w3.org/TR/REC-xml/#dt-chardata)
I quickly noticed some problematic cases (found in French maybe ok in
other languages) :
ProductRedExplanation (in Product association)
WebtoolsMessage2 (Webtools export)
WebtoolsMessage5 (Webtools import)
ManufacturingNote3 (Edit BOM)
There are certainly others, just a 1st approach
This also goes back to CSS style best practices. We shouldn't name
things "ProductRedExplanation" because it implies a color. What if a
stylesheet changed the text color to yellow? Then the name would not
make sense. It is better to use names like
"ProductHighlightedExplanation" to indicate the text is somehow
different, but without specifying its attributes.
-Adrian
