Hi :)
It might help to have a few people on both mailing lists (or whatever the
devs use to communicate between each other).
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.
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
documentation.
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
working.
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.
Regards from
Tom :)
On 16 December 2014 at 08:40, Michael Bauer <fios@akerbeltz.org> wrote:
Sgrìobh Sophie na leanas 16/12/2014 aig 07:23:
workload issue again and sent a mail to devs and UX to be careful with
our workflow. UX has set a page with string changes here:
https://wiki.documentfoundation.org/Documentation/RecentStringChanges
Those are actually all 'acceptable' and in fact, most look very welcome as
they down-geek the wording :-D
It's part of my job to smooth things in the project, and I'll really try
to do my best here.
Thanks for what you're doing. Feeling a bit more hopeful for the future!
Michael
--
*Akerbeltz <http://www.faclair.com/>*
Goireasan Gàidhlig air an lìon
Fòn: +44-141-946 4437
Facs: +44-141-945 2701
*Tha Gàidhlig aig a' choimpiutair agad, siuthad, feuch e!*
Iomadh rud eadar prògraman oifis, brabhsairean, predictive texting,
geamannan is mòran a bharrachd. Tadhail oirnn aig www.iGàidhlig.net
<http://www.xn--igidhlig-0ya.net> <http://www.iGaidhlig.net/>
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-
unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be
deleted
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-l10n] Cosmetic changes? (continued)
Re: [libreoffice-l10n] Workflow based on master · Valter Mura
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.