<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - In "Asian Phonetic Guide" dialog, Options in "Position" drop-down menu are mislabeled." href="https://bugs.documentfoundation.org/show_bug.cgi?id=142724#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - In "Asian Phonetic Guide" dialog, Options in "Position" drop-down menu are mislabeled." href="https://bugs.documentfoundation.org/show_bug.cgi?id=142724">bug 142724</a> from <a class="email" href="mailto:sophi@libreoffice.org" title="sophie <sophi@libreoffice.org>"> sophie</a> <pre>(In reply to Ming Hua from <a href="show_bug.cgi?id=142724#c4">comment #4</a>) > (In reply to Heiko Tietze from <a href="show_bug.cgi?id=142724#c3">comment #3</a>) > > Sure, RTL/LTR was just an example where we could find a "compromise" with > > odd/even instead of left/right. I cannot think of such solution for > > top/bottom other than translating "left" in terms of "top". That's why I set > > NOB, but feel free to reopen with a suggestion. > I see. But if you understood the problem properly, why would you dismiss > the simple "top" => "top/right" and "bottom" => "bottom/left" suggestion by > the reporter? Sounds a reasonable, if non-elegant, compromise to me. I agree with Ming here, this is a reasonable and less confusing solution than having labels in the UI not reflecting what they should do.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>