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


On Mon, Dec 2, 2013 at 2:37 PM, Sophie <gautier.sophie@gmail.com> wrote:

a) Can somebody layout precisely what an en_US l10n
team/group/individual would do?

as, I said, I think the first thing is to have an up to date glossary,
then check for the consistency in the menus/dialogs/tabs, check for the
Camel case use, check that the good terms are used for the good
functions, actions, etc and are consistent with the terms already used.
Check that the help buttons leads to help files, check that the help
files is up to date, etc. I've more but don't want to frighten you with
the tasks ;)

oh, is that all?

:P

So to answer Robinson and you, yes, we need somebody able to check the
en_US version. I'm ready to help in each step.


Awesome.

Sophie: please point us at whatever docs/intro info you have and we
can get started stubbing-in wiki pages, creating a list of TODO items,
etc. Feel free to poke us every week or so if you need something more
from us.

Thanks,
--R

-- 
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


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.