On Thu, Dec 5, 2013 at 10:52 AM, Robinson Tryon <bishop.robin...@gmail.com> wrote: > On Thu, Dec 5, 2013 at 4:37 AM, Mateusz Zasuwik <mzasu...@gmail.com> wrote: >> 2013/12/2 Sophie <gautier.sop...@gmail.com> >> >> And en-US team need glossary, surely. I see many inconsistent phrases like >> "*Please consider restart LibreOffice* to set new features". > > Soooo..what's the best way for me to identify and squash bugs in > strings like this? Should I just keep an eye on core.git? Perhaps > look at the compiled list of strings? >
During alpha and beta testing, and during translation process dozens of people read en-US strings. Some people report typo bugs either in Bugzilla, or in e-mail, and those bugs are fixed within hours. I don't think we need to set up processes, e.g. formal review, UI committee, approval, etc -- we had these in old OOo era -- , just we need to exercise the "many eyeballs" principle better. It is better to report a typo multiple times, than never. Cheers, Andras -- 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
