Need to replace the word e.g. with "for example" or "for instance" and i.e. with "that is" English literals in the in core/module N-R
Note: Frequently, the replacement of text with 'for instance' or 'for example' requires the re-wrapping of docblocks and code comments to be near but less than 80 characters.
| Comment | File | Size | Author |
|---|---|---|---|
| #31 | Replace-with-english-words-2640720-31.patch | 131.82 KB | ankitjain28may |
| #29 | Replace-with-english-words-2640720-29.patch | 132.56 KB | ankitjain28may |
| #2 | 2640720-2-fix-string-eg-d8.patch | 46.03 KB | lars toomre |
| #12 | 2640720-11.patch | 122.96 KB | imalabya |
| #14 | inetrdiff-2640720-12-14.txt | 31.83 KB | imalabya |
Comments
Comment #2
lars toomre commentedHere is an initial patch for this round. It covers all occurrences of 'e.g.' in core/modules/n* to r*.
Comment #3
lars toomre commentedLink to Round 6 issue #2640960: Replace i.e. and e.g. with English words in /core/scripts, /core/tests & /core/themes directories
Comment #4
jhodgdonMostly looks great! A few small things to fix...
Before for example, there should be a ; not ,
should have a comma before "or"
Module descriptions are translatable strings. Let's leave this out of the patch.
Translatable string, leave out of patch.
vs. is not an abbreviation for "vis-a-vis", but "versus".
Let's not have translatable strings in the patch.
needs comma before "or"
Comment #5
jhodgdonAlso... As per discussion on that other issue... We need to limit the scope of this issue to only e.g. and i.e. fixes, and take out all the other fixes.
Comment #6
imalabyaComment #7
imalabyaComment #8
imalabyaHave changed the target folder irrespective of the first patch because anyways it was falling out of scope. Multiple folders are targeted because not too many instances are there in the folders combined.
Comment #9
jhodgdonI just reviewed a patch made by someone on a different issue. Please read the comment at #2640718-12: Replace i.e. and e.g. with English words in core/modules A-L before you make a patch here. It may be helpful. Thanks!
Comment #10
imalabyaComment #11
imalabyaThe patch resulted in a huge size of 125kb :(
Do we need to break it up more?
Comment #12
imalabyaComment #13
jhodgdonI think the patch size is OK. it is a bit large but the changes are fairly straightforward.
Needs a bit of work though:
example is misspelled here.
This is translated text and not API docs or comments. So, we should put this change in a separate issue/patch. Translated text strings cannot be changed in 8.0.x any more, and will only be accepted in 8.1.x until the first release candidate, so it's just easier if patches with translated text are kept separate from API docs changes.
Translated text -> new issue/patch
Translated text -> new issue/patch
needs comma after "is"
hm. I am not sure what "i.e." really meant here. The docs really don't make sense.
Maybe actually just delete the whole "i.e. they may still be loading" part? Because this says it's a callback to be called after they are done loading anyway. I think we should just delete that end of the sentence.
comma after example
comma after example
example is misspelled
no comma after decays I think?
This line needs rewrapping to under 80 chars
Also I don't think we want a comma after "methods" here.
I think the "for example, to log in the same user again" should be in () maybe?
I don't understand why "method" was inserted here. I think it should probably say:
This affects, for example, StreamWrapper...
In any case, "for example" should have commas before and after for this usage.
So the punctuation of
previous clause; for example, next clause
is only OK if the previous/next are really clauses or the "next clause" part is the end of the sentence.
It is not OK here, because there is more stuff after the "next clause" part.
Here I think you need to put (for example, KernelTestBase) in ()
this "for example, to log in..." part needs to be in ()
I think this would be better punctuated as:
button label; for example, ...
First line docs of functions and member variables need to be limited to 1 line.
So you'll need to either just omit the IMAGETYPE_JPEG part, or put it into a separate paragraph.
If you are making that one above into a separate paragraph, you could include this additional example in the paragraph. ;)
I am not sure that default and admin are the only possibilities, here, so probably we still need "for example" here?
See note above about first-line docs being 1 line.
The "For example" here should be up on the previous line.
Here too.
extra comma
I think this i.e. really was meant to be "for example" here?
here too
over 80 characters, rewrap
over 80, rewrap
extra space after ,
See earlier note about first-line docs being 1 line.
Here we can probably shorten it by making the paren part say:
(such as user or session ID)
see previous comment
The "for example" part should be in parens, not its own "sentence" (it's not a sentence).
Also please rewrap to nearly 80 char lines.
see previous note
extra space after comma
: should be ,
rewrap to 80 char lines
example is misspelled
should be
value; for example, views_handler_field_field
extra space after ,
needs comma after example
extra space after comma
We could really probably just get rid of the "that is" here.
example is misspelled
over 80 chars, rewrap
take out the , and space after (
Comment #14
imalabyahave addressed the above points.
Comment #15
jhodgdonMuch better, thanks!
I think there are only a few items that still need attention:
Um, I think this one is more of a "for example" than a "that is"? Sorry if I said the opposite in a previous review. ;)
The correct word here is "affects" (as in the original), not "effects" (as in the current patch).
We should really file a separate issue to remove the 2-3 duplicated lines in this test. Out of scope to do that in this issue, however.
; should be a , here
that is -> for example
that is -> for example
example is misspelled
; should be , here
Comment #16
sidharthapUpdated patch as per comment #15
Comment #17
jhodgdonWhen making a new patch on an issue that already had a patch, you really MUST make an interdiff file. Thanks!
Anyway... I tried to apply this patch to 8.2.x but it failed to find file core/modules/views/src/Test/PluginInstanceTest.php -- so I guess that needs to be removed from the patch.
That aside, I applied the patch (except that part), and there are a few other places that need fixing in modules N-V. Please be more careful in the future when making these types of cleanup patches to get *all* of the problems.
Anyway, here's the grep output, minus user interface text (which we need to do in a different issue) -- and file paths are relative to core/modules:
So, please fix these places, and make an interdiff file that goes back to patch #14, which is the last one I reviewed. Thanks!
Comment #18
imalabyaHi Jennifer, here is a re-rolled patch from #14.
Comment #19
imalabyaComment #20
jhodgdonHm. In the interdiff/patch in #18, I still do not see the item from node.module mentioned in comment #17. I didn't look for the other ones, but I would guess if you didn't do that one, you didn't do the others? Please check comment #17 again. Thanks!
Comment #21
imalabyaYep, missed those; hidden because I searched for e.g. and i.e. while these were e.g and i.e
Have added an updated patch with the changes as well.
Comment #22
jhodgdonOn #2637336-33: Replace i.e. and e.g. with English words in /core/includes and /core/misc directory, catch pointed out that we need a Coder/DrupalCS rule before any of these issues can be committed. See
https://www.drupal.org/core/scope#coding-standards
So I will delay reviewing any more on these issues until that is done.
Comment #27
avpadernoComment #28
ankitjain28may commentedThe patch in comment #21 is failed to apply.
Comment #29
ankitjain28may commentedThis will fix this.
Comment #31
ankitjain28may commentedThis will fix.
Comment #32
xjmThese issues need to be postponed until #2714651: Add a rule for replacing e.g. and i.e. with English words is resolved. Thanks!
Comment #41
quietone commentedAdding coding standards tag. Coding standards issues are typically tasks, changing category.