[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG Blocks||115596 --- Comment #7 from Heiko Tietze --- We discussed the topic in the design meeting. As comment 3 points out, the distinction is rather technical. And the term is used in MSO as well, so familiar to users. In the end it's up to translators to find a fitting localization. => NAB Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115596 [Bug 115596] [META] Labels of UNO commands bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 --- Comment #6 from John Mills --- Precisely what Eyal wrote. +1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 --- Comment #5 from Eyal Rozenberg --- "formatting", not "formattings", as it's a collective noun. And - I like "conditional formatting" much better than "conditional formats". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 --- Comment #4 from sophie --- (In reply to V Stuart Foote from comment #3) > However, as the en-US is the core for other translations, the requirement to > distinguish slips. Which way is it handled for translators. In general I > don't believe we are well served by massive string changes propagating as > l10n/i18n translation churn. > > IMHO => WF > > @Sophie? Thanks Tuomas for reporting and Stuart for the ping :) So if "the requirement to distinguish slips", there is no way to be sure that the right word will be used in future strings. In this case, I think it's up to translators to make the distinction if it exists in their language. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 V Stuart Foote changed: What|Removed |Added CC||so...@libreoffice.org --- Comment #3 from V Stuart Foote --- Not convinced. Yes in technical English there is a distinction to be made between nouns "format" and "formatting" where the root verb remains "format". E.g. "a particular data format requires specific data formatting" So could make a case for nuanced application, and selective string changes. However, as the en-US is the core for other translations, the requirement to distinguish slips. Which way is it handled for translators. In general I don't believe we are well served by massive string changes propagating as l10n/i18n translation churn. IMHO => WF @Sophie? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 Heiko Tietze changed: What|Removed |Added CC||fit...@ubuntu.com, ||jmill...@yahoo.com, ||vsfo...@libreoffice.org --- Comment #2 from Heiko Tietze --- Something for the native speakers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158290] "Formattings" should be used instead of "Formats" in some cases
https://bugs.documentfoundation.org/show_bug.cgi?id=158290 kdub changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #1 from kdub --- Hey Tuomas, Thanks for the suggestion. I have attached the UI/EX team for consideration on this. -- You are receiving this mail because: You are the assignee for the bug.
