https://bugs.freedesktop.org/show_bug.cgi?id=70339
Priority: medium
Bug ID: 70339
Assignee: [email protected]
Summary: Word boundary definition problem
Severity: normal
Classification: Unclassified
OS: All
Reporter: [email protected]
Hardware: Other
Status: UNCONFIRMED
Version: 4.1.1.2 release
Component: Linguistic
Product: LibreOffice
Created attachment 87382
--> https://bugs.freedesktop.org/attachment.cgi?id=87382&action=edit
Screenshot of problem
My problem is specifically with Scottish Gaelic but judging by the responses
from the Hunspell team, it's a general issue.
I have attached a screenshot of how certain items are handled by three
different applications (LibreOffice 4.1.1.2, Firefox 24, Opera 17 (now
Chrome-based)). All three have a different way of wrongly underlining certain
items which occur with a high frequency in Gaelic:
's th' bh' Bh' Th' 'S B' b' d' 'gam 'ga h-Alba n-aran t-aran
The .dic file contains (at least theoretically) all the necessary items for
these to be identified as correct forms:
's th' bh' b' d' 'gam 'ga
plus rules/tags which allow the prefixing of h- n- t- to certain items
h-Alba n-aran t-aran
But each application then goes and identifies an apparently random selection of
these and wrongly underlines them.
We'd assumed that the following settings should prevent this type of thing:
WORDCHARS -'’
# replace correct accented double vowels with unaccented ones for acceptance
ICONV 1
ICONV ’ '
But we were told that "WORDCHARS of Hunspell is not a system-wide setting" and
that "WORDCHARS is only for the command line Hunspell executable (in fact,
Hunspell library doesn't recognize WORDCHARS, but the Hunspell executable loads
the beginning of the affix file for a few extra settings). LibreOffice, Firefox
etc. use their own tokenization mechanism. Conversion beetwen character
encodings, word breaking of input texts are not part of the Hunspell library."
So it would seem something in LO needs fixing but I'm not sure what or where?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
