https://bugs.kde.org/show_bug.cgi?id=497653
--- Comment #8 from Valter Mura <[email protected]> --- Let's have some scenarios (for Italian translations). Suppose I have 3 translation projects and these projects have different translations' style rules (these are only mere examples): Project 1 - KDE: the translation team adopted a very friendly style, both for UI and Guides (using 1st person singular) Project 2 - LibreOffice: the translation team adopted a very friendly style for UI (1st person singular), but a more formal style for built-in Guide (2nd person plural) Project 3 - Gnome: is more formal, the team uses 1st person singular for commands and formal style for commands' descriptions (we call it: impersonal), and a formal style for Guide (impersonal) So, if I'm working on project 1, I need to choose its special style, but Lokalize could find/suggest also from the other styles, which could be slightly different due to the style adopted. Not only: it becomes difficult (in the sense of getting wrong strings), for the special Italian scenario, to use the feature "Fill with all exact suggestions" and "Fill with all exact suggestions and mark as fuzzy". Styles could also be different by categories: Legal jargon is different from medical jargon or computer jargon, so, especially in Guides, we need to make this difference. -- You are receiving this mail because: You are watching all bug changes.
