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

Hello Sophie, *,
On Mittwoch, 11. Dezember 2013 17:19 Sophie wrote:
I would like to open a discussion on the l10n workflow, the
quality of the en_US version and the Help files. All is linked and
I would like to discuss how we can improve the process here. I'm
sure that having a better understanding between the l10n process
and the dev process should help us to improve things :) So here is
a proposal, it's a bit long, sorry for that.

would this discussion not more suitable after the 4.2 release ;?

*Before updating Pootle:
- it's important for l10n team to know the approx load of work
that will be needed to achieve the whole work. Time between beta1
and rc1 is short and that will help to better organize this time
between translation and proof reading.


- it's exhausting when you think you are over and to see a new
bunch of words coming. Knowing it in advance help to manage the
time too


*About the en_US overall quality
- the process to rely on the l10n team to fix the en_US version is
ok, even if it gives us extra work to understand what is meant
before we realized it's a mistake. So it's also error prone for
all the translations. - but that doesn't solve the several typos
that already exist and that are overlooked by the l10n team (e.g
in the Character > Font Effect dialog, there is Overline _c_olor
and Underline _C_olor and this is the same for several dialogs)

Do not forget the double/triple/howmuchelse used mnemonics in the UI 
... ;)

- that doesn't solve also the lack of universal vocabulary used in
several dialogs (e.g Tab/Pane/Panel/Deck to name the same object
or Graphic/Picture/Image). I've nothing to propose here but to
define a glossary where developers could pick the good word but
I'm not sure it will be used

Yes, that would be really nice (especially, if we as translators 
would get it as well ... ;) ). It is really time consuming, what is 
meant with word $X and then finding out, that word $Y was used on 
other places ... :(

* About the help files
- I always wonder why there is a Help button on a new dialog when
no help file is appended ;)

And me is wondering, why there is not only a help button but also a 
help menu (as I am still a victim of, I am not sure, 
if there should be any difference between the two ... :( ). Both 
opens konqueror on my system, although I have installed the OLH ... 

- more and more functions are undocumented or their help is
obsolete. I always think that an undocumented function is lost for
the user and a sad thing for a developer because his function will
not be used as expected. May be, but I don't know how heavy it
would be for developers, the solution would be to open an issue
with a special tag like NF for each new feature, with three lines
about what the feature is supposed to do. Searching on BZ with
this special tag would allow to involve more people in the loop to
test it and document it.

Yes, please :) I also would like to see a short description for new 
function, that shortly explains it (and maybe a short example for it 
documented there as well) ... ;)
Thanks for your mail

God is dead and I don't feel all too well either....
                -- Ralph Moonen

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.