Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Hi Tom,
Le 16/12/2014 10:09, Tom Davies a écrit :
Hi :)
It might help to have a few people on both mailing lists (or whatever the
devs use to communicate between each other).

That's what I'm supposed to do, but I think you've noticed it :)

That way maybe one of those people might notice when one of the mailing
lists starts talking about doing something that might have an impact on one
of the other mailing lists they are on.

yes, and I'm constantly discussing the string changes with the UX team
(mostly Jay and on IRC). Because of the openness of our project, anybody
can suggest a change without being aware of the impact it can have for
other team or sometime even for the product. Cor is monitoring a lot on
Bugzilla about those changes and he is dedicating a lot of his time.

On the Accessibility Mailing List a few days ago there was mention that one
of the recent breakages could be fixed by adding a tiny bit of text into
the menu items.  I warned them that;
1.  it would impact on the translators who were struggling with a similar
issue right now.
2.  if they could get their changes in within a couple of days then it
might neatly fit into the work the translators are doing right now and thus
avoid duplication
3.  that if they couldn't get their UI changes in right now then it would
be better to wait a few months, or longer, in the hope that the translators
might get some automation to handle it.

The result seems to be that they have given up on getting that improvement
through :(  NOT the result i'd intended because i think Accessibility is
also crucial and it gets far less support than translators or

The trick is to add the shortcuts to the menu label in order for them to
be read by screen readers. Whether it will be done or not will depend on
who will open the issue and implement it. Stuart is part of the Design
team, so he is aware of the l10n team request about massive changes, but
I will monitor it.

Imo it would have been great if the current set of changes had been
coordinated with stuff that the other teams need.  There is already a
system to try to coordinate between teams but it doesn't seem to be

What system are you talking about?

I think if it was backed-up by having a few people liaising between a
couple of mailing lists, and a couple other people liaising between a
couple of other mailing lists then it might be easier to coordinate between
the teams.

The only way to coordinate is to do cross communication between the teams :)

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.