The proper use of 'e.g.' and 'i.e.' are confusing and reportedly are one of the most frequent sources of mistakes editors see in technical writing/documentation. Drupal's docblock and code documentation includes some examples of incorrect usage as well.
Let's start to correct some of that confusion by replacing 'e.g.,' by what it means in English: 'for instance,'. This will require a number of patches until 'e.g.' is appropriately replaced. Based on the first round, the patch size should be around 50k.
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.
Comments
Comment #2
lars toomre commentedRelated issues in sequence of rounds:
- #2640960: Replace i.e. and e.g. with English words in /core/scripts, /core/tests & /core/themes directories
- #2640966: Some fixes for 'e.g.' in docblocks and code comments - Round 8
Comment #3
jhodgdonI know you like to fix up other problems at the same time... but in the last few of these patches I've reviewed, I could have marked the patch RTBC if not for some fixes to other stuff that weren't quite right. So maybe consider just doing "e.g." in the "e.g." patches, and not venturing into adding missing return/param docs, fixing up other problems, etc.?
Also please do not include translatable strings in the patches. We can't commit changes to translatable strings to every version of Drupal, and also just because we don't like "e.g." very much is not a great reason to invalidate 160+ translations of that string on localize.drupal.org.
Thanks!
Comment #4
lars toomre commentedAdded #2645178: Fix 'e.g.' and 'i.e.' usage in user-facing strings as a holding area for the user-facing string changes.
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.
Comment #7
jhodgdonThis series of issues is badly scoped. I am just going to close them. Sorry.