I know I should not be surprised at the lack of response, but I want to stress the lack of thought that went into the important issue of converting document 'tables' (from the 'old' GDocs to the 'new' GDocs) in a way that did not force the user to spend a lot of wasted time reformatting what should have been done in the conversion itself.

This one is particularly outrageous:

To summarize, when new rows are added to a converted table, one becomes aware that Google Docs' way of converting tables apparently uses a specific 'padding' spec built into the conversion process (0.069) when formatting the cells in the new row(s).  This spec can easily be different than the padding that's in the converted table.  As such, text entered in the cells in these new rows/columns, does not align with the text in the cells above or below it.  The user has to manually 'fix' this by going into the Table Properties menu and adjusting the padding 'value.'  That would be bad enough, but wait!, worse is yet to come -- are you ready for this? -- YOU CAN'T REFORMAT CELLS IN ENTIRE ROWS OR COLUMNS (AS A UNIT) -- YOU HAVE TO REFORMAT EVERY CELL INDIVIDUALLY.

The Three If's:

If the absurdity of the foregoing is somehow lost on the bright bulbs of Google, then what more is there to say . . .

If this way of converting tables were a project in 'intelligent design' (not the theological kind) at even your local community college, Google would flunk with flying colors.

If necessary, I will post and share a document illustrating this issue.