Date: prev next · Thread: first prev next last


First of, I work on translation myself, alone in translating into Swedish at the moment, so I'm well aware of these translation issues. ;)

In this particular case I believe that we can avoid extra workload on the translation team. At least when it comes to the change/fix that I have in mind. The problem in this case is strictly a Windows accessibility issue were the shortcut string is already displayed in the menu entries but not forwarded to accessibility tools. Now what I believe needs to be done is to find the correct place to actually forward the information, it is already forwarded on Mac and Linux. Finding the correct place to change is not that easy, but I believe that it can be done without effecting the translation team. Again I'm not taking about adding new strings to menu entries just use the information that is already present and present it to accessibility tools as well.

Note that I'm swamped with work (at my daytime job) and when I get some spare time I need to work on the translation and spend time with my ~4 months old baby girl. This is also one of the reasons why I thought a bug should be filed so we can keep track of the bug, and I can add my findings as I try to narrow in on the issue. Thereby also making it easier for someone else to complete the work if I can't find the time.

Niklas Johansson

Tom Davies skrev den 2014-12-16 14:15:
Hi :)
Ok, so best left for a couple of months.

I have a feeling we might have managed to stay "on topic", or at least get
back to the original problem!  However that is so rare i can't quite
believe it!

@ Niklas, does that address the issue at all?

Regards from
Tom :)

On 15 December 2014 at 10:44, Sophie <> wrote:
Hi Tom, all,
Le 14/12/2014 22:53, Tom Davies a écrit :
Hi :)
L10n lists are currently having a massive argument/discussion (discussion
is more accurate tbh) right now about the disruptive effect of minor
The problem is minor changes, like capital letters in menu entries, that
concerns only en_US version but because this version is the source for
all the localization, this is also visible in localized versions where
it could be considered as wasted time for localizers.
I'm not sure but i suspect that getting such a UI change within the next
couple of days might play out ok and catch the translators before they
put too much time into too many strings and then finding they need to
repeat the work.

If it's not likely to be just a couple of days then it'd probably be
for them if this sort of change didn't happen for a few months - or
longer.  There might be a chance of them automating something like this
it'd take ages to set something up and they haven't agreed on getting the
automation bit sorted.
Shortcuts can't be automated as they are localized (Ctrl and Shift). And
the problem with automation is that we need somebody to write the
scripts ;) The same for accelerators, where we need to adapt them to
translated words.
Anyway we will have a discussion about it with developers and UX team,
once we are out of the 4.4.0 rushes.

Sophie Gautier
Co-founder - Release coordinator
The Document Foundation

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.