Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On 07/29/2013 08:49 AM, Krunoslav Šebetić wrote:
The second field in the header of a suffix class means only allowed
combination with prefix flags (from a class with similar allowed
prefix-suffix combination), so your first example will work (with
syntax corrections) well:

FLAG long
SFX A1 Y 1
SFX A1 0 a .

SFX A2 Y 1
SFX A2 0 e .

Just to see if I got it right, hunspell will not try to combine suffixes (A1 + A2) but only add declared ones to a .dic entery.

Think I got it, the in .aff I should put

FLAG long
SFX A1 N 1
SFX A1 0 a .

and then suffixes will not combine mutually.

And also in

    SFX A1 0 a e

SFX stands for suffix, A1 is the flag, 0 stands for "no striping", "a" standrs for "add 'a' ", and "e" is condition: if word ends with "e"?

Just need a confirmation...

In example above, there is only one "FLAG long", so it needs to be put only once in .aff file, before firs SFX?

Only in space separated form, and in LibreOffice this is only for
better suggestions.

What about entery in .dic like (in one row):

    Word1/C2 Word2/C2

No, there is that autocorrect list in the file DocumentList.xml of
acor_hr-HR.dat ZIP archive.

Will find that, it's not in bundle I've downloaded...



To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.