I agree that this should be done but the core team probably feel that there are 'bigger fish to fry'. You could put in a pull request in GitHub and take that task on. I'm sure it would be appreciated.

My first stab at GitHub... I'll try it.

These may be auto generated from LESS, so best to check that with someone from the core before doing it, or you could be wasting your time.

I'm not sure I understand your reference to LESS. Are you saying that the core team use LESS in their development environment and that's where the truncation is happening?

I'm not the slightest bit worried about the quality of the css found in typography.css in the default theme files but I do see lots of inconsistencies throughout the core css files in [root]/concrete/css. Does the css spec mandate a trailing semicolon?

I can see some instances where leaving it off can cause problems but I'm sure there are also tons of add-ons that are inconsistent as well. You might be chasing your tail on this one.

I usually come at best practices from a "How To Teach A Novice" perspective. When teaching CSS, it's paramount that a novice gets into the habit of *always* remembering the trailing semicolon when making CSS declarations. If not, it is easy to waste time scratching heads and pulling hair wondering why styles are not showing up as expected.

LESS is used in the core. But I don't know if it is just the dashboard (bootstrap derived) or also in any of the themes.

Hence my caution to find out more before putting effort into changes.

Yeah... it's a simple fix but you're right - if they're using LESS then it's a fix that would have to happen every new version they push out, I assume.

It's a generally accepted best practice for optimisation to save a few bytes (more trouble than it's worth IMHO).

e.g.http://www.queness.com/post/588/15-ways-to-optimize-css-and-reduce-...

This is what I assumed - an attempt to save "a few bytes". But MHO agrees with you - more trouble than it's worth.