Re: [libreoffice-l10n] Proposal: Glossary's Terminology Guidelines

Hello Antonio,

I agree that the glossary feature is very helpful and that it's 
occasionally misused. However, I disagree with the proposed solution. 
The proper solution IMO would be to disallow translators from modifying 
other languages' glossaries by default:
https://github.com/WeblateOrg/weblate/issues/8807

That way we wouldn't have to first try to formulate a universal glossary 
policy which takes into account the idiosyncracies of every possible 
language and then try to get every translator (many of whom probably 
don't read this mailing list) to follow it.

Whether each language team should translate reserved words in 
programming, Calc functions, or whatever, should be IMO completely up to 
that language team. Also, "never translate this term" is not necessarily 
a good universal rule because of transliterations etc. I don't know 
what's considered best practice in translation for all 100+ languages LO 
supports, but luckily I don't have to: I believe each language team 
knows that best. The tool we use (Weblate) should respect that.

Best regards,
Tuomas

Antonio Vidal kirjoitti 21.3.2024 01:15:
> Glossary are helpful because there are terms which could cause 
> mistranslations, such as BASIC and Calc functions in sbasic and scalc, 
> however there aren't rules to creating a glossary, which could cause 
> warnings such as
>
> > DO NOT USE THE “TERMINOLOGY” CHECKBOX UNLESS IT’S REALLY WARRANTED!
> >
> > PLEASE DON’T CROSS YOUR TEAM’S BOUNDARIES AND ADD GLOSSARY STRINGS 
> > ONLY TO YOUR OWN GLOSSARY, NOT TO EVERYONE ELSE’S, UNLESS STRICTLY 
> > NECESSARY
> > https://translations.documentfoundation.org/translate/libo_ui-master/glossary/en/?checksum=fa4ca0895bb6cde7
>
> Docs for Glossary: 
> https://docs.weblate.org/en/latest/user/glossary.html
>
> - Untranslatable terms: Use this for brand names or other terms that 
> should not be changed in other languages
> - Forbidden translations: Use this to clarify translation when some 
> words are ambiguous or could have unexpected meanings
> - Terminology: Use this for important terms that should be 
> well-thought-out, and retain a consistent meaning across all languages
>
> Would like to propose guidelines for creating Terminology terms:
>
> SHOULD: What should be in Terminology
>
> - Code variables/functions such as BASIC and Python terms should be 
> Untranslatable terms + Terminology
> - Excel/Calc functions
>
> SHOULDN'T: What should not be in Terminology
>
> - Adjectives, prepositions, articles, verbs, and non-concrete nouns 
> (common words in general)
>
> Up to discussion:
>
> - Should we use for LibreOffice UI elements/labels/menu such as layout, 
> emphasis, home...?
> - While Markdown, Python, Wiki are brand names, translations software 
> such as DeepL and Google/LibreTranslate generally don't translate them, 
> thus adding a glossary is unnecessary
>
> If proposal accepted: add key points in 
> https://wiki.documentfoundation.org/Translating_LibreOffice
>
> Antonio Vidal (NamelessGO)

--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy