<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Be able to see different measurement units for line versus page properties (e.g. pt and in)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=72662#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Be able to see different measurement units for line versus page properties (e.g. pt and in)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=72662">bug 72662</a> from <a class="email" href="mailto:lukebenes@hotmail.com" title="Luke <lukebenes@hotmail.com>"> Luke</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=72662#c9">comment #9</a>) > And those individual units would have to be stored anyway. Plus we need an > option to switch from point to something else, in to cm was only one example. Agreed, which is why I proposed that we have 2 classes, a general measurement unit of in. or cm.(page, margin, ruler dimensions etc.) And a typography class where point is commonly used(line spacing, font, line width etc.). This alone would solve my use case and the use case described by the bug reporter. Making the UI easier to change these 2 classes is fine, but I'm opposed to modifying the UI without first addressing this underlying issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>