<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - What is the difference between a "Styles deck" and a "Styles window"?" href="https://bugs.documentfoundation.org/show_bug.cgi?id=131078#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - What is the difference between a "Styles deck" and a "Styles window"?" href="https://bugs.documentfoundation.org/show_bug.cgi?id=131078">bug 131078</a> from <a class="email" href="mailto:sdc.blanco@youmail.dk" title="sdc.blanco@youmail.dk">sdc.blanco@youmail.dk</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=131078#c6">comment #6</a>) > When you talk about LibreOffice you mean documentation. Yes. Only documentation. > Or do you also suggest to change the original terms, actually the guideline? No. Previously I used the word "technical" as a way to indicate the specific terminology used by UX/developers. My queries do not concern this terminology. But maybe there is an implicit query about whether the user documentation must/should always use the same terminology as the guidelines. (In reply to Buovjaga from <a href="show_bug.cgi?id=131078#c7">comment #7</a>) > What do you think about bringing this topic up on the localisation mailing > list? I could do it. Could be a good idea, if a consensus develops toward something that might require a non-trivial number of retranslations (e.g., introducing a consistent word use). You can better evaluate whether that list should also be involved in making the consensus.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>