Bug 159551 - LanguageTool Premium doesn't work when account uses a plus email address
Summary: LanguageTool Premium doesn't work when account uses a plus email address
Status: RESOLVED DUPLICATE of bug 158117
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-04 15:06 UTC by Martin W
Modified: 2024-02-04 15:19 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin W 2024-02-04 15:06:27 UTC
Description:
Whilst it is possible to use LanguageTool Premium with a plus email address, e.g., username+languagetool@domain.name, LibreOffice will not work with this.

Setting up LibreOffice for a premium account works, but automatic checking doesn't work, i.e., no spelling or grammar checking is performed.

Replacing the plus address with a standard one resolves the issue. Nonetheless, LibreOffice should wotk with plus addresses, as defined in the RFC 5233 Sieve: Subaddress Extension.

Steps to Reproduce:
1.Enter LanguageTool Premium credentials as described here: https://languagetool.org/insights/post/product-libreoffice/
2. Disable all other writing aids.
3.Load a test document, or simply type, and no autocorrect suggestions are displayed.
4.Change LanguageTool account to a non-plus address, restart LibreOffice Writer, and retest. A

Actual Results:
No highlighting for spelling and grammar.

Expected Results:
Spelling and grammar errors should be underlined.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 4fe86607b5ac922e55f140471fda9b60bdaa980d
CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded

LanguageTool support contacted to check the API.
Comment 1 Mike Kaganski 2024-02-04 15:19:45 UTC

*** This bug has been marked as a duplicate of bug 158117 ***