Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
On Wed, Jan 28, 2015 at 5:22 PM, Rimas Kudelis wrote: > Hi again, > > On 2015 m. sausio 28 d. 09:09:27 EET, Rimas Kudelis wrote: >> >> >>On 2015 m. sausio 28 d. 08:10:38 EET, jonathon >>wrote: >>> >>>BTW, when you say "style guide", which specific one do you mean? >> >>The one you're looking for, assuming it exists. If not, or could be a >>combination of Gnome HIG and any American English style guide we (the >>LibO community) would deem acceptable and meeting our needs (e.g. The >>Chicago Manual of Style). > > In fact, I just thought that it doesn't even have to be a formal manual: if > somebody would be willing to oversee style consistency in our strings, and > that style would look acceptable by our en-US users, then why not? Especially > if that person would be willing to formalize these rules into a written style > manual along the way. > > -- > Rimas This document may be of interest: https://obriend.fedorapeople.org/WritingStyleGuide/ It's only recently (last year) been open sourced and made public. On the Docs list, I wrote: Here is one I remember from OOo: https://wiki.openoffice.org/wiki/Documentation/Dashboard/Help_Style_Guide There is also a short (and somewhat out of date) writing style guide for LO user guides. It is Chapter 5 in the LO Docs Contributors Guide. See here: https://wiki.documentfoundation.org/Documentation/Development#Contributors_Guide In Docs, we mainly referred to the relevant sections of _Read Me First! A Style Guide for the Computer Industry_ by Sun Technical Publications. --Jean -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
Hi again, On 2015 m. sausio 28 d. 09:09:27 EET, Rimas Kudelis wrote: > > >On 2015 m. sausio 28 d. 08:10:38 EET, jonathon >wrote: >> >>BTW, when you say "style guide", which specific one do you mean? > >The one you're looking for, assuming it exists. If not, or could be a >combination of Gnome HIG and any American English style guide we (the >LibO community) would deem acceptable and meeting our needs (e.g. The >Chicago Manual of Style). In fact, I just thought that it doesn't even have to be a formal manual: if somebody would be willing to oversee style consistency in our strings, and that style would look acceptable by our en-US users, then why not? Especially if that person would be willing to formalize these rules into a written style manual along the way. -- Rimas -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
Le 28/01/2015 08:09, Rimas Kudelis a écrit : > > > On 2015 m. sausio 28 d. 08:10:38 EET, jonathon > wrote: >> >> On 28/01/15 05:18, Rimas Kudelis wrote: >> >>> I really don't see a revision of all existing strings as a >> requirement to start reviewing newly added ones. >> >> At some point in time that review has to be done. To minimize the >> overall workload, it is easier, and simpler, to do it before >> reviewing newly added strings, than afterwards. (For starters, >> doing it afterwards means having to review those newly added >> strings at least twice, and maybe thrice.) > > > You're right, but if the choice is between no reviews at all and > reviews of new strings only, which would you choose? It's go for the > latter. > >>> Especially if you are a native English speaker and have a style >>> guide >> at hand. >> >> Just as the English language has never met it word that it has not >> adopted as it's own, so it has never met a grammatical construct >> that it has not adapted and mutilated. One direct consequence of >> both those facets of acquisition, is that it is incredibly >> difficult to write a sentence in English that is grammatically >> incoherent, but extremely easy to write a sentence that >> grammatically means the opposite of what was intended. >> >> IOW, that certain string might be "clear, concise and >> grammatically, syntactically and typographically correct", but >> mean something other than intended, because the vocabulary is >> usually used to mean something else elsewhere. > > Let's add "semantically correct" or "contextually correct" to my list > of requirements then. :-) > >> BTW, when you say "style guide", which specific one do you mean? > > The one you're looking for, assuming it exists. If not, or could be a > combination of Gnome HIG and any American English style guide we (the > LibO community) would deem acceptable and meeting our needs (e.g. The > Chicago Manual of Style). I still have the one for French but it's copyrighted Sun anyway (from 2006). Gnome HIG contains a lot of information that we can use easily. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
On 2015 m. sausio 28 d. 08:10:38 EET, jonathon wrote: > >On 28/01/15 05:18, Rimas Kudelis wrote: > >> I really don't see a revision of all existing strings as a >requirement to start reviewing newly added ones. > >At some point in time that review has to be done. To minimize the >overall workload, it is easier, and simpler, to do it before reviewing >newly added strings, than afterwards. (For starters, doing it >afterwards >means having to review those newly added strings at least twice, and >maybe thrice.) You're right, but if the choice is between no reviews at all and reviews of new strings only, which would you choose? It's go for the latter. >>Especially if you are a native English speaker and have a style guide >at hand. > >Just as the English language has never met it word that it has not >adopted as it's own, so it has never met a grammatical construct that >it >has not adapted and mutilated. One direct consequence of both those >facets of acquisition, is that it is incredibly difficult to write a >sentence in English that is grammatically incoherent, but extremely >easy >to write a sentence that grammatically means the opposite of what was >intended. > >IOW, that certain string might be "clear, concise and >grammatically, syntactically and typographically correct", but mean >something other than intended, because the vocabulary is usually used >to >mean something else elsewhere. Let's add "semantically correct" or "contextually correct" to my list of requirements then. :-) >BTW, when you say "style guide", which specific one do you mean? The one you're looking for, assuming it exists. If not, or could be a combination of Gnome HIG and any American English style guide we (the LibO community) would deem acceptable and meeting our needs (e.g. The Chicago Manual of Style). -- Rimas -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/01/15 05:18, Rimas Kudelis wrote: > I really don't see a revision of all existing strings as a requirement to > start reviewing newly added ones. At some point in time that review has to be done. To minimize the overall workload, it is easier, and simpler, to do it before reviewing newly added strings, than afterwards. (For starters, doing it afterwards means having to review those newly added strings at least twice, and maybe thrice.) >Especially if you are a native English speaker and have a style guide at hand. Just as the English language has never met it word that it has not adopted as it's own, so it has never met a grammatical construct that it has not adapted and mutilated. One direct consequence of both those facets of acquisition, is that it is incredibly difficult to write a sentence in English that is grammatically incoherent, but extremely easy to write a sentence that grammatically means the opposite of what was intended. IOW, that certain string might be "clear, concise and grammatically, syntactically and typographically correct", but mean something other than intended, because the vocabulary is usually used to mean something else elsewhere. BTW, when you say "style guide", which specific one do you mean? jonathon -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUyH1ZAAoJEKG7hs8nSMR7cv0P/Rws6m/2XmSKBTbMk4FWtN+e CZCw8Ch92t91+T8ih76PxIaAa0YKvpMoC7oV/j8mhDcYkHbzV+LGv0DgQkS0uxu1 Fi/v18w8b+JgnRbISBSmiZ3Bnhgi2dLONTLH4JUAuqRjGbMmteNVqjcV61C4fO+P AFxOn8HUZJy2vdNpYmEGi9uvsOwWXvgiTFF8vnBOyI+6nv0gPYjbCFBXmBlylYwf cjGdbORnwhfLJ5c6zQkFvZh74ffMEcqfQl63Flw7WV1nSc6JbVfDVn7jrvG1jp3k 4sycs/I0Tlja1biPuevwa2JBMT3+HudUCSZvh7MwhQ3SZ0liD2W8/bx64q9RPd68 Nk9NLXXilhTA/4xhR84/ViodxBJ6xzZakbU2Ln7HMvF3CwFTFf1ezJoR5PujYUcK WfnCH2/oWwkKa6f+LSIT3Dx3AIoI6vBG49yeCoZHmr5+1G2TEcvfQnxuischk7/r nHpPuMbFmV9FLrc4hOnYIwuCB7WzsMNpmyBjwfKUjNwFtozHhzLO011jyMBje3GM g7akbPdTPOqpeSrJ22v3dehjkUX9i+b6bhWf43Bt7NfnOn/keT6FNx6WhmuMQL7H pt4cHRUHvWdX++w+/VF2omTJFqNEBfQcvKlUISFlTd/BQWlIh4SkYq4L6p9siGLM lghc+axFELCpcksUKP0i =sCY8 -END PGP SIGNATURE- -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
Hi Jonathon, 2015.01.27 23:15, jonathon wrote: > On 27/01/15 18:36, Rimas Kudelis wrote: > > >> If you need to review *all* help & UI, I think it maps to an equivalent of a 500 or more page handbook. > > But you don't. L10n only are only asking for review of strings when they are being changed. > > Review strings in context. > > Whoever volunteers for this task will need to go through _all_ of the > existing help, UI, and other things, before reviewing strings when they > are changed. > > The task requires: > * Copy editing; > * Line editing; > * Proof reading; > amongst other editing tasks. > > FWIW, this also means that the l10n, a11y, and i18n teams will be dumped > with a slew of changes that might, but probably won't affect their > existing translation, but will still need to be verified to ensure that > their translations, etc. are not broken. I really don't see a revision of all existing strings as a requirement to start reviewing newly added ones. Of course, it would be beneficial, but not at all a requirement. You don't need to read a 500-pages worth of text to tell whether or not a certain string is clear, concise and grammatically, syntactically and typographically correct. Especially if you are a native English speaker and have a style guide at hand. Rimas -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/01/15 22:57, Robinson Tryon wrote: > So basically there's a steep learning curve, I wouldn't describe it as "a steep learning curve" as much as it is ensuring that the current text is grammatically correct en_US, with no spelling errors, _and_ conforms to the conventions in the Style Manual. Rephrased: The person has to translate everything into en_US, then copyedit everything. > but once someone has an active knowledge of the current text, then they should be able to do work in small deltas. In theory, once everything is in en_US, and conforms to the style manual, then the only "knowledge" required, will be to read the material once or twice, before being able to work on small deltas. >As long as there's clear documentation about getting up to speed (and the potential time to do so), the workflow seems plausible. That initial translation & copyedit is there, purely because of a number of minor issues. Things that 99.99% of the users probably won't notice, but overall detract from the project. The things that one is not conscious of, but nonetheless have a negative impact. > I keep on hearing about these big changes. Some of them sound scriptable, but > have there been some that are not? Presentation markup is usually scriptable. Vocabulary, spelling, syntax, and grammatical changes are not scriptable. (Well they can be, but you end up with "invisible, insane" for "out of sight, out of mind".) > If it's more of an official-ish document, perhaps this would be a better home: > https://wiki.documentfoundation.org/TDF/Manual_of_style My sense is that whilst Sun wanted the project to use it, it's usage was honoured by the breach thereof. jonathon -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUyCcaAAoJEKG7hs8nSMR7574P/33IUFp8P5gyXtrvLN9laX/V dAxkn5emxpkbjcbPAYEYun6VCYKe34TI4TXNqeDiXMP6J1jGwRCs24XeDbxrlRzZ T/MctfVmlLrjbBnsLKW+sKA3KW5Hl4wGfh9tyZcWPc1eMBN9iEiqmsCUPw3ZN3+t //eTmXWMcVt22KzyPNtOhUcFOWZAZiz/J8kc4cve/QCbxIujOyiVxL038zwFgb3O 2XRFZe+3bVophvSka3kep088TXQjO0bSBCUHw+kNQmbwYykZld5nrF5sumjBlqXl xMer//vRyPI56+WztBCl6WgmW+HfxTh4b8/vycb0Cbxzn2IxnnTgVzp8+uFJ0B/T lz26N7WlHd4J86swMtSEwoW6T0z7d2dJj26hopYLQQ3NDVRfefksnP6GiVcMi6rh ozOQjZayJE66Z8DMDt79wW8cVbvM+YwgZxZySOnQCC/viP8+e1RrsCOkVuXKu+kK r9JdmfMkbkkxeDcmXendM3aKMOaHKseqIn/Br1HwcY140rvrG2UW8VGAWHT5LSNU H34tL8yhN3yELFTI9RflA4BTsIpN0m3Vt8fmsAzFi3hQZ+DetRnHmUlvonNzS9er 9fnDjnp4EfjmUVPRkushCr8PB4/aj7o9Nf0AznXy1wbdBBgmVWoUFSuw5WQZrWoM tVst8Fo4K7KYcQBwiy6j =xU5C -END PGP SIGNATURE- -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
On Tue, Jan 27, 2015 at 4:15 PM, jonathon wrote: > On 27/01/15 18:36, Rimas Kudelis wrote: >>> If you need to review *all* help & UI, I think it maps to an equivalent of >>> a 500 or more page handbook. >> But you don't. L10n only are only asking for review of strings when they are >> being changed. > > Review strings in context. > > Whoever volunteers for this task will need to go through _all_ of the > existing help, UI, and other things, before reviewing strings when they > are changed. So basically there's a steep learning curve, but once someone has an active knowledge of the current text, then they should be able to do work in small deltas. As long as there's clear documentation about getting up to speed (and the potential time to do so), the workflow seems plausible. > The task requires: > * Copy editing; > * Line editing; > * Proof reading; > amongst other editing tasks. Yup, sounds challenging. > FWIW, this also means that the l10n, a11y, and i18n teams will be dumped > with a slew of changes that might, but probably won't affect their > existing translation, but will still need to be verified to ensure that > their translations, etc. are not broken. I keep on hearing about these big changes. Some of them sound scriptable, but have there been some that are not? Aside from the bulk-changes, how many string additions/modifications/etc.. are there on a weekly or monthly basis? > BTW, does anybody know where the *current* _LibreOffice Manual of > Style_ can be obtained from? Once we find it, let's add a redirect here: https://wiki.documentfoundation.org/Manual_of_style (Or it can live there, if it doesn't have a good home yet! :-) If it's more of an official-ish document, perhaps this would be a better home: https://wiki.documentfoundation.org/TDF/Manual_of_style Best, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/01/15 18:36, Rimas Kudelis wrote: >> If you need to review *all* help & UI, I think it maps to an equivalent of a >> 500 or more page handbook. > But you don't. L10n only are only asking for review of strings when they are > being changed. Review strings in context. Whoever volunteers for this task will need to go through _all_ of the existing help, UI, and other things, before reviewing strings when they are changed. The task requires: * Copy editing; * Line editing; * Proof reading; amongst other editing tasks. FWIW, this also means that the l10n, a11y, and i18n teams will be dumped with a slew of changes that might, but probably won't affect their existing translation, but will still need to be verified to ensure that their translations, etc. are not broken. BTW, does anybody know where the *current* _LibreOffice Manual of Style_ can be obtained from? jonathon -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUx//eAAoJEKG7hs8nSMR7id0P/1PegxvPm//5nkOUyarAncy5 kk1XCAcu/V2ACHW+DmcMlHWZo8Yfq1otKZWZ8NN7zE9ooqSv/j2jIk6zSFbwgZpo jCzQr5YX2T0dJNn9JblKlZSzTEtom+fb571J4kSWzrIt9NI7r0tTr5iRJVTmgMix Ohqt55zTq0RJqaZGu+Y3MtLVKxeqcuthBsJN1V0GYFDvNClk9A/WeflOq4u4E9zU dItu3wYeUp5iK/HNBnVdNoz6dnRA8SYWSZvrXS4PnJw4WLI8OizsJcX622M4ys42 ToXWloi32ZNEdHtYxvmI7iuzOG7IuWQcZqVRdNmPqwh5mv8RfS9MWoGwWo6UXeJQ ZvahsEMpMjUutxN01pqz3j6HkSC5Z+wlGzhFDmJK8x6m/z6CwWNZtj3UsVpUDlH2 whn9mDsfZUdaJl7zA5GlE0OxqBugJA0FSS3jvVb9lBz+sMg2eM3m6MVJ+iR0pB/L X0mLnU8wgKjX+b5SW5VGtyccgZhcmbCOq4UD+TX8PxANHJrV8J7SL0OznL+bmhsq scYag/J8SctQnmAxXwMgERx2jpUBvZEVRposG2TSk54i7CVL9Jk09RGJutT9+Lv+ EmpFj4bjpdFtNUY4tfxRs77AHSHkbDA67mVsSFGNaNDqrX7bOGCqLFfISP4IIpj3 WR6e50byTlZEy1zj1uUs =ANfD -END PGP SIGNATURE- -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
Hi, 2015.01.27 15:39, Olivier Hallot rašė: > On 26/01/2015 10:06, Robinson Tryon wrote: >> On Mon, Jan 26, 2015 at 6:48 AM, Olivier Hallot >> wrote: >>> On 19/01/2015 08:03, Sophie wrote: To conclude, what l10n team would like to see is: - a review process of the strings before they are committed and make sure they respect the en_US standards (capitals, grammar, punctuation, typography). Maybe adding the Gnome HIG book to our pages [like 2] if not already. >>> That will require a revisor with en_US skills. >> About how much work (read: time) would this review process entail? >> >> Thanks, >> --R >> >> > If you need to review *all* help & UI, I think it maps to an equivalent > of a 500 or more page handbook. > But you don't. L10n only are only asking for review of strings when they are being changed. Rimas -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
Hi Robinson On 26/01/2015 10:06, Robinson Tryon wrote: > On Mon, Jan 26, 2015 at 6:48 AM, Olivier Hallot > wrote: >> On 19/01/2015 08:03, Sophie wrote: >>> To conclude, what l10n team would like to see is: >>> - a review process of the strings before they are committed and make >>> sure they respect the en_US standards (capitals, grammar, punctuation, >>> typography). Maybe adding the Gnome HIG book to our pages [like 2] if >>> not already. >> >> That will require a revisor with en_US skills. > > About how much work (read: time) would this review process entail? > > Thanks, > --R > > If you need to review *all* help & UI, I think it maps to an equivalent of a 500 or more page handbook. -- Olivier Hallot Comunidade LibreOffice http://ask.libreoffice.org/pt-br -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
On Mon, Jan 26, 2015 at 6:48 AM, Olivier Hallot wrote: > On 19/01/2015 08:03, Sophie wrote: >> To conclude, what l10n team would like to see is: >> - a review process of the strings before they are committed and make >> sure they respect the en_US standards (capitals, grammar, punctuation, >> typography). Maybe adding the Gnome HIG book to our pages [like 2] if >> not already. > > That will require a revisor with en_US skills. About how much work (read: time) would this review process entail? Thanks, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Workflow between dev, UX and l10n teams
Hi Sophie, OK for me to work on master translation. On 19/01/2015 08:03, Sophie wrote: > To conclude, what l10n team would like to see is: > - a review process of the strings before they are committed and make > sure they respect the en_US standards (capitals, grammar, punctuation, > typography). Maybe adding the Gnome HIG book to our pages [like 2] if > not already. That will require a revisor with en_US skills. > > - if there is a way to script changes, script them otherwise wait until > there is a script available to commit them > > - any time there are heavy changes that pop up in someone's mind (like > changing ... for …) discuss it with the l10n team before committing > those changes. Right. The issue is raised (IMHO) because a great deal of developers are not english native speakers, as well as their focus is no C++ language rather than English. The thing is: if we can catch the modification upfront, it will make it easy for all of us. If I may also suggest, I'll ask all developers and within ESC recurrent revision, to check/review/flag for any major issues with respect to l10n. This can be implemented as One: create a meta-bug about l10n en_US string revision. Two: then on each commit that involves some form of l10n activity, the developer should open a new bug with his commit number/reference and link to the l10n meta-bug. The subject line should be "L10n revision requested". Three: the same developer, if implementing or modifying a feature, should also open a similar bug with subject "[LOCALHELP] feature XYZ changed/created; help page missing" and link to bug 80430. Note that we don't ask to the developers to fix english mistakes nor write help pages, tasks that we can offload from them provided we get noticed. Fixing English mistakes/linguistics and writting help pages is a task the community can do continuously. Kind regards -- Olivier Hallot Comunidade LibreOffice http://ask.libreoffice.org/pt-br -- To unsubscribe e-mail to: projects+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/projects/ All messages sent to this list will be publicly archived and cannot be deleted
