The version 5.9 of LanguageTool and any snapshot afterwards don’t work with portable version of LO. I see the following exception:
LT office integration log from Mon Oct 24 03:37:29 CEST 2022
LanguageTool 6.0-SNAPSHOT (2022-10-23 16:42:55 +0000, dc05200)
OS: Windows 8.1 6.3 on x86
LibreOffice 7.3.6.2 (The Document Foundation), de
Java-Version: 1.8.0_351, max. Heap-Space: 247 MB, LT Heap Space Limit: 222 MB
getLTDictionaryFile: LT dictionary file doesn't exist: start to create
CacheIO: getCachePath: documentPath == null!
MultiDocumentsHandler: getNumDoc: Document 0 created; docID = 1
Time to generate cache(4): 467
Time to generate LT spelling file: 966
setLtDictionary: Create LT spelling dictionary __LT_de-DE_internal1.dic
Internal LT dicitionary for language de-DE added: Number of words = 154494
Time to generate dictionary: 4402
LanguageToolMenus: setActivateRuleMenu: event id: 1504
TextLevelCheckQueue: run: Interrupt ended
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException: Could not check sentence (language: German (Germany)): <sentcontent>Dein Mutter ist schon. </sentcontent>
at org.languagetool.MultiThreadedJLanguageTool.performCheck(MultiThreadedJLanguageTool.java:217)
at org.languagetool.JLanguageTool.checkInternal(JLanguageTool.java:987)
at org.languagetool.JLanguageTool.check(JLanguageTool.java:906)
at org.languagetool.JLanguageTool.check(JLanguageTool.java:891)
at org.languagetool.openoffice.SwJLanguageTool.check(SwJLanguageTool.java:216)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog.getSpellErrorInParagraph(SpellAndGrammarCheckDialog.java:557)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog.getNextSpellErrorInParagraph(SpellAndGrammarCheckDialog.java:519)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog.getNextErrorInParagraph(SpellAndGrammarCheckDialog.java:487)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog.access$6700(SpellAndGrammarCheckDialog.java:96)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog$LtCheckDialog.getNextError(SpellAndGrammarCheckDialog.java:1902)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog$LtCheckDialog.gotoNextError(SpellAndGrammarCheckDialog.java:1626)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog$LtCheckDialog.access$6300(SpellAndGrammarCheckDialog.java:844)
at org.languagetool.openoffice.SpellAndGrammarCheckDialog$LtCheckDialog$9.run(SpellAndGrammarCheckDialog.java:1444)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException: Could not check sentence (language: German (Germany)): <sentcontent>Dein Mutter ist schon. </sentcontent>
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
at org.languagetool.MultiThreadedJLanguageTool.performCheck(MultiThreadedJLanguageTool.java:214)
... 13 more
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Could not check sentence (language: German (Germany)): <sentcontent>Dein Mutter ist schon. </sentcontent>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:593)
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
... 14 more
Caused by: java.lang.RuntimeException: Could not check sentence (language: German (Germany)): <sentcontent>Dein Mutter ist schon. </sentcontent>
at org.languagetool.JLanguageTool$TextCheckCallable.getOtherRuleMatches(JLanguageTool.java:1989)
at org.languagetool.JLanguageTool$TextCheckCallable.call(JLanguageTool.java:1862)
at org.languagetool.MultiThreadedJLanguageTool.lambda$null$1(MultiThreadedJLanguageTool.java:200)
at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1424)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703)
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172)
Caused by: java.lang.RuntimeException: Could not create hunspell instance. Please note that LanguageTool supports only 64-bit platforms (Linux, Windows, Mac) and that it requires a 64-bit JVM (Java).
at org.languagetool.rules.spelling.hunspell.DumontsHunspellDictionary.<init>(DumontsHunspellDictionary.java:45)
at org.languagetool.rules.spelling.hunspell.Hunspell.getDictionary(Hunspell.java:50)
at org.languagetool.rules.spelling.hunspell.HunspellRule.init(HunspellRule.java:585)
at org.languagetool.rules.de.GermanSpellerRule.init(GermanSpellerRule.java:1506)
at org.languagetool.rules.spelling.hunspell.HunspellRule.ensureInitialized(HunspellRule.java:559)
at org.languagetool.rules.spelling.hunspell.HunspellRule.match(HunspellRule.java:220)
at org.languagetool.rules.de.GermanSpellerRule.match(GermanSpellerRule.java:1424)
at org.languagetool.JLanguageTool.checkAnalyzedSentence(JLanguageTool.java:1366)
at org.languagetool.JLanguageTool.access$1500(JLanguageTool.java:74)
at org.languagetool.JLanguageTool$TextCheckCallable.getOtherRuleMatches(JLanguageTool.java:1946)
... 7 more
Caused by: java.lang.UnsatisfiedLinkError: dumonts.hunspell.bindings.HunspellLibrary.Hunspell_create(JJ)J
at dumonts.hunspell.bindings.HunspellLibrary.Hunspell_create(Native Method)
at dumonts.hunspell.bindings.HunspellLibrary.Hunspell_create(HunspellLibrary.java:25)
at org.languagetool.rules.spelling.hunspell.DumontsHunspellDictionary.<init>(DumontsHunspellDictionary.java:39)
... 16 more
LanguageToolMenus: setActivateRuleMenu: event id: 608
CacheIO: getCachePath: documentPath == null!
I found this ticket, describing a similar situation. Probably we have something like this also here.
So, my questions are: is it possible to correct this, without having a 64-bit version? Because at the PortableApps, they don’t like 64-bit versions because they don’t give any advantages, according to them.
The other solution would be to provide a portable 64-bit version of LO, but I don’t know how to make Jon T. Haller reconsider this and release an 64-bit version of portable LO.