<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Default set of table styles" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101349#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Default set of table styles" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101349">bug 101349</a> from <a class="email" href="mailto:tietze.heiko@gmail.com" title="Heiko Tietze <tietze.heiko@gmail.com>"> Heiko Tietze</a> <pre>(In reply to andreas_k from <a href="show_bug.cgi?id=101349#c19">comment #19</a>) > I'd like to separate the table styles into two areas While the paragraph styles provides an hierarchical organization we do not have it for other types. And actually going with only two top-level categories (print and screen) makes not much sense to me. On the other hand I fully agree with a couple of _plain_ styles. But in the end it's up to the user to choose the right one and to layout the document. Table styles are not capable to align depending on the content (numbers, text, currency...), you would have to provide different variants, which is awkward IMHO. Table style can define padding but not the column/table width and row height. Check out <a href="https://design.blog.documentfoundation.org/2015/12/13/style-your-tables/">https://design.blog.documentfoundation.org/2015/12/13/style-your-tables/</a> And finally I would wait for the outcome of the survey. We want to keep the community involved rather than design by committee. That doesn't mean that the likely high-rated "Scientific" style cannot be refined or supplemented later. But if the users down-vote "3D", for instance, we shouldn't invest much in this variant.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>