Sophie 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. Seems to me that a lot of that could be checked by a script. Some of it should be flagged when testing using the various screen readers. (I am making some very broad assumptions about the extent of a11y testing. Starting with using a box that literally has no monitor, keyboard, or mouse hooked up to it, when checking to see what functionality broke this time around.) >Check that the help buttons leads to help files, check that the help files is >up to date, etc. IOW, a lot of grunt work that probably could have been automated years ago, but wasn't. >> b) Is there an existing en_## L10N group that could assume the >> responsibilities, duties, etc of an en_US L10N group? >there is an en_GB group, but we are speaking about en_US which is the source >for all languages. There is no en_US l10n group because this is the developer >team in fact, My thinking was that the en_## L10N group could add slidestream this into their localization work >good linguist. You don't want a linguist here. You want somebody that suffers from anb acute case of monolingualism. jonathon -- Sent from the eating establishment at the Far side of the Universe, at the begining of Time, and at the end of Space. -- To unsubscribe e-mail to: l10n+unsubscr...@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
