W dniu 2014-07-17 06:12, Kumara Bhikkhu pisze:
> Excellent answers. I'm no native speaker, but hope you don't mind me adding.
>
> Perhaps the only place where LT could *suggest* a comma after "for
> example" is when it begins the sentence.

I think there will be also genuine cases of a missing comma whenever 
"for example" is followed by a noun or an adjective.

Best,
Marcin

>
> kb
>
> Mike Unwalla wrote thus at 02:13 AM 17-07-14:
>> I agree that 'for example' does not have to be followed by a comma.
>> Sometimes, 'for example' is at the end of a sentence.
>>
>> You can write this, for example.
>>
>> Regards,
>>
>> Mike Unwalla
>> Contact: www.techscribe.co.uk/techw/contact.htm
>>
>>
>> -----Original Message-----
>> From: Robin Dunn [mailto:rd...@iparadigms.com]
>> Sent: 16 July 2014 17:35
>> To: development discussion for LanguageTool
>> Subject: Re: help with English style rules
>>
>> Hi,
>>
>> I am a native English speaker and I agree with the answer at the
>> following link which advises 'for example' does not always have to
>> be followed by a comma.
>>
>> http://english.stackexchange.com/questions/132359/any-exception-with-commas-before-and-after-for-example
>>
>>
>> >From the link here's an example of a valid case where a comma is
>> not required after 'for example':
>>
>> "While it is common practice to do recalibration between trials, for
>> example in reading research, this is not always possible or feasible."
>>
>>
>> I'm not aware of a complete comprehensive English grammar guide
>> which is freely available online but I think
>> english.stackexchange.com is an excellent resource for these kinds
>> of questions.
>>
>> Regards
>> Robin
>>
>>
>>
>>
>> On Wed, Jul 16, 2014 at 5:04 PM, Daniel Naber
>> <daniel.na...@languagetool.org> wrote:
>>
>>
>>          Hi,
>>
>>          someone suggests that "for example" should always be followed by a
>>          comma:
>>          https://github.com/languagetool-org/languagetool/issues/136
>>
>>          My question to the English native speakers:
>>
>>          1.) Do you agree with this?
>>
>>          2.) Is there an established style guide that we can use as
>> a reference
>>          for questions like these? If possible, it should be available on the
>>          internet for free, and it should also be comprehensive
>> enough to answer
>>          most questions.
>>
>>          Regards
>>            Daniel
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Languagetool-devel mailing list
>> Languagetool-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Languagetool-devel mailing list
> Languagetool-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>
>


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Languagetool-devel mailing list
Languagetool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/languagetool-devel

Reply via email to