Re: [libreoffice-l10n] Localizing "Community Edition" branding in LO71

2020-12-20 Thread Heiko Tietze
The brand string is part of the images. Could be done for the SVG, in theory, 
but not in case of the splash screen, which is and has to be raster graphics 
(PNG). Well, nothing is impossible in informatics but the effort should be balanced.
But moreover it makes not much sense to translate brand names in general. 
"Gemeinschaftsversion" in German sounds totally weird. We had an eye on l10n 
while choosing the name so the term is kind of inter lingua, hopefully.
And last but not least, this brand image is not used for any binary version 
built by TDF. It's just what we ship with the code.


On 19.12.20 18:05, Martin Srebotnjak wrote:

Community Edition


--
Dr. Heiko Tietze, UX-Designer and UX-Mentor
Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint


--
To unsubscribe e-mail to: l10n+unsubscr...@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


Re: [libreoffice-l10n] Localizing "Community Edition" branding in LO71

2020-12-20 Thread Martin Srebotnjak
Well, Heiko, there is nothing "interlingua" about "Community Edition" ...

We will have to find a way around it.

Lp, m.

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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


[libreoffice-l10n] Translation of acronyms

2020-12-20 Thread Paul Roos
Hi,
I think that most languages that use the Latin alphabet, follow the rule
for all IT related acronyms should always ...
(a) Be kept in the original English language as in most of the technical
published literature, acronyms are written in uppercase.
(b) The word BASIC is a good example. It is the name of a programming
language and stands for *B*eginners *A*ll-purpose *S*tandard *I*nstruction
*C*ode.
(c) If one saves the translation as BASIC it also causes the extra
frustration, that it is flagged as "Unchanged", which means that you have
to reset it and then save it. This applies to all acronyms.
(d) Another issue why BASIC, in particular, is an important example: BASIC
= programming language and basic (lowercase) means "not complicated".  See
the ambiguity?
Regards,
Paul

-- 
To unsubscribe e-mail to: l10n+unsubscr...@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