Bugfix: show grid allocation on full width

When the object is as wide as the surrounding area,
the grid allocation was not shown.

Also: grid conflict is now a warning
Grid: draw conflicting grid cells in red

This makes it much easier to spot difficulties with the
grid.

The automagic table is replaced by a more or less
sparse table which now holds the number of times
a grid cell is used.
More translations, no functionality changes

I'ts about time to do more translations, mainly
in grid.lua
Grid: fix allocation matrix

Much stricter now - which means it reveals 
many errors...
Bugfix: objects too wide

Rounding helps on border cases where we have floating
points such as 55.00000001 which results (with 
the ceil() function) in non-correct widths.
Bugfix on sp compare: remove source files

We must remove the source files before splitting
the source pdf into png. Let's say the current run produces
2 pages and the run before that 8 pages, the
last 6 files are left on the filesystem and 
confuse the page counter afterwards, which results
in a broken compare command.
Fix a QA testcase

No need for width anymore - the width of 10 was
just too wide for the page and the bug went unnoticed.

Now that we have a stricter grid algorithm, bugs as these
will show up.
Bugfix/Workaround: don't split when allocate == no

When allocate == no we don't do splitting. While this is not perfectly
obvious and clear, it helps in border cases when we know we are doing 
something evil.
Merge branch 'grid' into develop

*  Bugfix/Workaround: don't split when allocate == no
*  Fix a QA testcase
*  Bugfix on sp compare: remove source files
*  Bugfix: objects too wide
*  Grid: fix allocation matrix
*  More translations, no functionality changes
*  Grid: draw conflicting grid cells in red
*  Bugfix: show grid allocation on full width