Re: svn commit: r1745006 [3/9] - in /openoffice/trunk/main

2016-05-22 Thread Marcus
Am 05/22/2016 11:16 PM, schrieb Pedro Giffuni: I'm not Dennis but dare to answer. - I have had those changes in my HD for a least a couple of months now, I was tired of them, - I considered dropping them but it was quite some effort (time), and the changes I did to codespell are not public

RE: svn commit: r1745006 [3/9] - in /openoffice/trunk/main

2016-05-22 Thread Pedro Giffuni
Hi Dennis; So you noticed such changes are burdensome ... The situation is more or less this so that you understand: - I have had those changes in my HD for a least a couple of months now, I was tired of them, - I considered dropping them but it was quite some effort (time), and the changes I

RE: svn commit: r1745006 [3/9] - in /openoffice/trunk/main: ./ accessibility/inc/accessibility/standard/ autodoc/inc/ary/idl/ avmedia/source/framework/ basctl/source/basicide/ basctl/source/inc/ baseg

2016-05-22 Thread Dennis E. Hamilton
In reviewing these 9 SVN reports a bit more closely than simply checking the -/+ lines, I see that these mechanical changes miss some material ones, if clarity of language is the goal. I also observe that some of the grammatical cases are typical of ways some non-native English speakers

RE: svn commit: r1745006 [3/9] - in /openoffice/trunk/main: ./ accessibility/inc/accessibility/standard/ autodoc/inc/ary/idl/ avmedia/source/framework/ basctl/source/basicide/ basctl/source/inc/ baseg

2016-05-22 Thread Dennis E. Hamilton
It is extremely difficult to review these omnibus patches, especially since some of the language problems that are preserved are distracting. At the same time, it is too easy to just want to assume that there is no incorrect change buried among all of the fixes to "wich", "initalize" and other

RE: svn commit: r1745006 [1/9] - in /openoffice/trunk/main: ./ accessibility/inc/accessibility/standard/ autodoc/inc/ary/idl/ avmedia/source/framework/ basctl/source/basicide/ basctl/source/inc/ baseg

2016-05-22 Thread Dennis E. Hamilton
@pfg and anyone else tempted to do any more of this, 1. Please do not create omnibus commits that, however easy to produce, a. Are awfully burdensome to review b. Are not tied to focused bugzilla issues providing an account of particular defects c. Do not have anything