Hunspell dictionaries unavailable in LibreOffice

  • Open
  • quality assurance status badge
Details
3 participants
  • Efraim Flashner
  • Ludovic Courtès
  • Roman Riabenko
Owner
unassigned
Submitted by
Ludovic Courtès
Severity
important
Merged with
L
L
Ludovic Courtès wrote on 9 Jan 2022 21:29
(address . bug-guix@gnu.org)
87ilus1wly.fsf@inria.fr
Hi!

When running something like:

guix shell hunspell hunspell-dict-fr libreoffice -- libreoffice

Hunspell dictionaries (for French in this case) are unavailable from the
spell-checking menu, even though DICPATH is set (this is with
92faad0adb93b8349bfd7c67911d3d95f0505eb2).

I think this is a relatively recent regression, but I’m not sure.

Am I missing something?

Thanks,
Ludo’.
E
E
Efraim Flashner wrote on 12 Jan 2022 19:21
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 53147@debbugs.gnu.org)
Yd8cOL1sOxtsVlPt@3900XT
On Sun, Jan 09, 2022 at 09:29:29PM +0100, Ludovic Courtès wrote:
Toggle quote (17 lines)
> Hi!
>
> When running something like:
>
> guix shell hunspell hunspell-dict-fr libreoffice -- libreoffice
>
> Hunspell dictionaries (for French in this case) are unavailable from the
> spell-checking menu, even though DICPATH is set (this is with
> 92faad0adb93b8349bfd7c67911d3d95f0505eb2).
>
> I think this is a relatively recent regression, but I’m not sure.
>
> Am I missing something?
>
> Thanks,
> Ludo’.

Does libreoffice also need to have the native-search-paths defined for
hunspell's search paths?

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmHfHDQACgkQQarn3Mo9
g1Hy7w/+KZI0AXZOInwl3/k7AeE+MpAXJf53EJV0stUzm4NDY4sFz7OOn+6c1qYf
sIG+Rpb7+AW2jL2W/nzw7JR5kN0JSTT15mYv85VFJoWW8+0reQH2ZHrlLpQK0gQO
gRX0RCiyeBEPJihgaw4ReM8UXPaX6KU1rhOAl3ldBwfZXsRZyRGHJ7kinGNvHpVI
zQ6j/iun4EcjrF0DG2oSAf/h/0y7hoW4/nTxXmrYZYSkDje8tlFMnBpo1KSx5Lks
YS+0K7KmufZqKFYZzMAIEFL359tmZbMezpn38eHiaCwNNNBBtpUUnEmVjM+5T7WX
UCeoxPqr7u0E4wimgnPLVGCbmNfAttjLUlUAs/tb8nWVQ5IewjUzgHVBZJuTAvZs
k6flRU0lsKxFG27iSwVAk7JZFFJqDeE5hQcFzA3YN86//cFBWEhnDuCjrtUxqYLe
rvpf0iiFBT3pDQUQYk1q1zj0gvbx2/EIZ6TOl82GZQdF/b5mYC7FRWJToUl2VI8A
25K266t3OKXaWSngsdkPlSIsuFD9gi7gWoiZ03Y7s4D0B2FPZAvoo7VFEAOWuiAX
2+8Ohg1h5n0Gq01h7jlXx2OMSsDGbny3VkSCRI2YR+Dm5XYdab1eC7bILAIGvTpA
cbylh9fuWuxKqwDhUJ/d7zGVAfhen9T9duD/m9Y+DtlFEYzzOyI=
=hQql
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 12 Jan 2022 22:07
(name . Efraim Flashner)(address . efraim@flashner.co.il)(address . 53147@debbugs.gnu.org)
87r19cpssc.fsf@gnu.org
Hi,

Efraim Flashner <efraim@flashner.co.il> skribis:

Toggle quote (11 lines)
> On Sun, Jan 09, 2022 at 09:29:29PM +0100, Ludovic Courtès wrote:
>> Hi!
>>
>> When running something like:
>>
>> guix shell hunspell hunspell-dict-fr libreoffice -- libreoffice
>>
>> Hunspell dictionaries (for French in this case) are unavailable from the
>> spell-checking menu, even though DICPATH is set (this is with
>> 92faad0adb93b8349bfd7c67911d3d95f0505eb2).

[...]

Toggle quote (3 lines)
> Does libreoffice also need to have the native-search-paths defined for
> hunspell's search paths?

We could do that, but with the ‘guix shell’ command above it wouldn’t
make any difference (‘DICPATH’ is indeed set).

Ludo’.
L
L
Ludovic Courtès wrote on 18 Jan 2022 11:12
control message for bug #53147
(address . control@debbugs.gnu.org)
878rvdl5e5.fsf@gnu.org
severity 53147 important
quit
L
L
Ludovic Courtès wrote on 19 Jan 2022 23:04
Re: bug#53147: Hunspell dictionaries unavailable in LibreOffice
(address . 53147@debbugs.gnu.org)
87iluf9ycl.fsf@gnu.org
Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (8 lines)
> When running something like:
>
> guix shell hunspell hunspell-dict-fr libreoffice -- libreoffice
>
> Hunspell dictionaries (for French in this case) are unavailable from the
> spell-checking menu, even though DICPATH is set (this is with
> 92faad0adb93b8349bfd7c67911d3d95f0505eb2).

Another data point: Hunspell itself does find the dictionaries:

Toggle snippet (9 lines)
$ guix shell -C hunspell-dict-{de,fr,pl} hunspell -- hunspell -D
SEARCH PATH:
.::/gnu/store/nkzscw3rb7ypm4a1f6ljx8lvpkssv8va-profile/share/hunspell:/usr/share/hunspell:/usr/share/myspell:/usr/share/myspell/dicts:/Library/Spelling:/home/ludo/.openoffice.org/3/user/wordbook:/home/ludo/.openoffice.org2/user/wordbook:/home/ludo/.openoffice.org2.0/user/wordbook:/home/ludo/Library/Spelling:/opt/openoffice.org/basis3.0/share/dict/ooo:/usr/lib/openoffice.org/basis3.0/share/dict/ooo:/opt/openoffice.org2.4/share/dict/ooo:/usr/lib/openoffice.org2.4/share/dict/ooo:/opt/openoffice.org2.3/share/dict/ooo:/usr/lib/openoffice.org2.3/share/dict/ooo:/opt/openoffice.org2.2/share/dict/ooo:/usr/lib/openoffice.org2.2/share/dict/ooo:/opt/openoffice.org2.1/share/dict/ooo:/usr/lib/openoffice.org2.1/share/dict/ooo:/opt/openoffice.org2.0/share/dict/ooo:/usr/lib/openoffice.org2.0/share/dict/ooo
AVAILABLE DICTIONARIES (path is not mandatory for -d option):
/gnu/store/nkzscw3rb7ypm4a1f6ljx8lvpkssv8va-profile/share/hunspell/pl_PL
/gnu/store/nkzscw3rb7ypm4a1f6ljx8lvpkssv8va-profile/share/hunspell/fr-classique
/gnu/store/nkzscw3rb7ypm4a1f6ljx8lvpkssv8va-profile/share/hunspell/de_DE

Stracing ‘soffice’ shows that it searches the ‘share/hunspell’
directories too. Now to find why it’s not doing anything with them.

Ludo’.
R
R
Roman Riabenko wrote on 9 Apr 2022 18:16
Re: Hunspell dictionaries unavailable in LibreOffice
e32b3329633cbf8759c40282ab575a04ba1e3c2d.camel@riabenko.com
Hello

? ??, 2022-01-09 ? 21:29 +0100, Ludovic Courtès ????:
Toggle quote (2 lines)
> I think this is a relatively recent regression, but I’m not sure.

Please note that there is a similar open issue from 2020:

Roman
L
L
Ludovic Courtès wrote on 23 Sep 2022 22:05
control message for bug #53147
(address . control@debbugs.gnu.org)
87y1u9eu0m.fsf@gnu.org
merge 53147 41390
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53147@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53147
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch