Menu

#146 False positives with wasn't, hadn't etc.

1.9
closed-works-for-me
nobody
5
2013-06-25
2012-11-06
No

I encountered the following bug today.
When typing a phrase like: "His girlfriend hadn't left him.", Languagetools underlines "hadn't" for me. When right clicking, I am informed that "The word hadn should probably be uppercase: "Hadn"."

I do not know why this error is caused, since, to me, it makes no sense. For troubleshooting purposes: The language I selected for the document was English UK, my localization (though this shouldn't play a role) is german (since I live in switzerland) and the interface language is Standard English (USA). In Languagetools, my selected mother tongue is "English". I have enabled all options in the languagetools options, so it may be that one of the selections makes this go haywire.

Note: The same problem also occurs with wasn't. I assume that it occurs in other instances though, but I haven't checked this yet.

Discussion

  • Mark Internom

    Mark Internom - 2012-11-06

    Image showing the error

     
  • Mark Internom

    Mark Internom - 2012-11-06

    Note: I have confirmed that this error also occurs when using "didn't".

     
  • Daniel Naber

    Daniel Naber - 2012-11-08

    I cannot reproduce this - is this the stand-alone version of LT? Could you attach a screenshot maybe?

     
  • Mark Internom

    Mark Internom - 2012-11-16

    Actually, dnaber, I already did when I made the bug report. The file is entitled: languagetoolsv19_bug.png, and shows the blue underline and the text that appears when you right click on it.

     
  • gulp21

    gulp21 - 2012-11-18

    I can reproduce the problem in the stand-alone version when English (GB) is selected as language. No problem is reported when any other variant of English is selected.

     
  • Daniel Naber

    Daniel Naber - 2012-11-18
    • assigned_to: milek_pl --> nobody
     
  • Daniel Naber

    Daniel Naber - 2012-11-18

    Sorry for not noticing the screen shot... I still cannot reproduce the problem here. Which version of OpenOffice or LibreOffice are you using? Could you attach the *odt file that shows the error?

     
  • Marcin Miłkowski

    Can you still replicate this in LO with LT 2.0? I have used en-gb, but the error is not shown at all.

    The cause of the bug must be some mistake in sentence segmentation but it's hard to say where it is.

     
  • Daniel Naber

    Daniel Naber - 2013-06-25

    Cannot reproduce without an *odt file that shows the problem.

     
  • Daniel Naber

    Daniel Naber - 2013-06-25
    • status: open --> closed-works-for-me
     

Log in to post a comment.