On 01/08/14 17:46, Laszlo Papp wrote: > On Wed, Jan 8, 2014 at 9:49 PM, Mark Brown <broonie@xxxxxxxxxx> wrote: >> On Wed, Jan 08, 2014 at 09:08:44PM +0000, Laszlo Papp wrote: >>> On Wed, Jan 8, 2014 at 9:02 PM, Laszlo Papp <lpapp@xxxxxxx> wrote: >> >>>> That being said, I will not have time, nor the motivation to argue >>>> over such a nuance, so feel free to reject the change. >> >>> Of course, this is just on top of the vim spell checker error as I >>> wrote in the commit message... >> >>> Oh yes, and one more factual data in here: >> >>> lpapp ~/Projects/linux-staging $ grep -rn "e\.g\." . | wc -l >>> 3447 >> >>> lpapp ~/Projects/linux-staging $ grep -rn " eg," | wc -l >>> 18 >> >> That's not the issue - it's dropping the comma. It's either "e.g." or >> "eg", the comma is a separate thing providing a break between clauses. >> Strictly it should have the periods since it is an abbreviation but >> their use is more vauge in fixed point text since they look ugly, the >> thing that made me complain was that you dropped the comma as well as >> substituting in the expanded version. > > I still do not get what point you are trying to make. Could you please > provide evidence? Because really, this is the usage I have seen in > projects out there all around, including the majority of the linux > kernel. > > Here is some more data: > > grep -rn "e\.g\. " . | wc -l > 2553 > lpapp ~/Projects/linux-staging $ grep -rn "e\.g\.," . | wc -l > 573 > -- Hi, I am used to seeing e.g. and i.e. always followed by a comma when they are used to begin a sentence. However, I just checked and some online style guides say to omit the comma and some say to use it, and we (Linux kernel) don't really have a writing style guide to look at. I think that makes it up to the maintainer to decide what is acceptable. -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
