correct Ctrl+Shift <> Shift+Ctrl ?

Hi all,

When creating a piece of new Help text, I saw that the sequence of key
combinations in Help is not consequent.

For example this page

https://help.libreoffice.org/6.1/en-US/text/scalc/04/01020000.html?&DbPAR=CALC&System=UNIX
I would expect Ctrl+Shift to be used consequent.

I can see the current situation as either funny or sloppy.
Correcting would of course show 'new' strings to translate.

Opinions?

Ciao - Cor

This is yet another per-platform convention: Linux (Gtk+) and macOS
put Shift first, and Windows puts Ctrl first.

I’d say the majority wins, so correct everything to “Ctrl+Shift”.

To ease the extra work, I volunteer to fix affected translations
accordingly, I just need admin permissions in Pootle.

Adolfo

Hi,

is that really an error? Do all 100+ l10n teams have time and resources for
that?

Should not the focus be on missing help topics and function descriptions,
if they exist?

Lp, m.

V V sre., 3. okt. 2018 ob 00:04 je oseba Adolfo Jayme Barrientos <
fito@libreoffice.org> napisala:

Hi Cor,

I personally don't see enough benefits for the energy spent by
translators reviewing hundreds of keystrokes like this in the Help,
unless an automated and transparent procedure can be put in place, as
Adolfo suggest.

Hi Adolfo,

Actually if it is a System convention, then we should use

<switchinline select="sys">
   <caseinline select="MAC">
       <item type="keycode">Shift + Command</item>
   </caseinline>
   <defaultinline>
       <item type="keycode">Ctrl + Shift</item>
   </defaultinline>
</switchinline>

Perhaps defining an <variable> with the lines above can be good too. Use
<embedvar> where it is needed. Translate once, use many.

PS: And another <variable> for the 100's of "LibreOffice - Preferences"
x "Tools - Options" ...

Regards
Olivier

Martin Srebotnjak (<miles@filmsi.net>) kirjutas 3.10.2018 kell 11:29:

is that really an error? Do all 100+ l10n teams have time and resources for
that?

Should not the focus be on missing help topics and function descriptions,
if they exist?

Seconded.
It doesn't in practice "matter" which key you press first, Shift or Ctrl,
so please, pretty please don't make us review all those strings again.

If this can be done via a script that updates all the translations too,
then it could be considered. But in that case I kindly ask that the script
be shared with those of us who translate offline.

Also, FWIW, also Linux/KDE uses Ctrl+Shift+... so IFF it can be automated
across translations, then Oliver's suggestion would be nice.

Best regards,
Mihkel