[lingu-dev] Hunspell 1.1.2

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

[lingu-dev] Hunspell 1.1.2

nemeth-2
Hi,

Thanks for the strict Debian policy, Hunspell 1.1.2 has been completed:

https://sourceforge.net/project/showfiles.php?group_id=143754

Thanks for the contribution.

Laci

Notes (also with Hunspell 1.1.1):

2005-11-11: Hunspell 1.1.2 release:

  - Bug fixes (MAP Unicode, COMPOUND pattern matching, ONLYINCOMPOUND
    suggestions)

  - Checked with 51 regression tests in Valgrind debugging environment,
    and tested with 52 OOo dictionaries on i686-pc-linux platform.


Changes:
        * src/hunspell/affixmgr.*: fix Unicode MAP errors (sorted only n-1
          characters instead of n ones in UTF-16 MAP character lists).
          Bug reported by Rene Engelhard.

        * src/hunspell/affixmgr.*: fix infinite COMPOUND matching (default char
          type is unsigned on PowerPC, s390 and ARM platforms and it will never
          be negative). Bug reported by Rene Engelhard.

        * src/hunspell/{affixmgr,suggestmgr}.cxx: fix bad ONLYINCOMPOUND
          word suggestions.
        * tests/onlyincompound.sug: empty test file to check this fix.
          Bug reported by Bj?rn Jacke.

        * src/hunspell/affixmgr.cxx: fix backtracking in COMPOUND pattern
matching.
        * tests/compound6.*: test files to check this fix.

        * csutil.cxx: set bigger range types in flag_qsort() and flag_bsearch().

        * affixmgr.hxx: set better type for cont_classes[] Boolean data (short
-> char)

        * configure.ac, tests/automake.am: set platform specific XFAIL test
          (flagutf8.test on ARM platform)



Release Name: 1.1.1

Notes:
2005-11-09: Hunspell 1.1.1 release:

  - Compound word patterns for complex compound word handling and
    simple word-level lexical scanning. Ideal for checking
    Arabic and Roman numbers, ordinal numbers in English, affixed
    numbers in agglutinative languages, etc.
    http://qa.openoffice.org/issues/show_bug.cgi?id=53643

  - Support ISO-8859-15 encoding for French (French oe ligatures are
    missing from the latin-1 encoding).
    http://qa.openoffice.org/issues/show_bug.cgi?id=54980

  - Implemented a flag to forbid obscene word suggestion:
    http://qa.openoffice.org/issues/show_bug.cgi?id=55498

  - Checked with 50 regression tests in Valgrind debugging environment,
    and tested with 52 OOo dictionaries.

  - other improvements and bug fixes (see ChangeLog)



Changes:
improvements:
        * src/hunspell/affixmgr.*: new and improved affix file parameters:

        - COMPOUND definitions: compound patterns with regexp-like matching.
          See manual and test files: tests/compound*.*
          Suggested by Bram Moolenaar.
          Also useful for simple word-level lexical scanning, for example
          analysing numbers or words with numbers (OOo Issue #53643):
          http://qa.openoffice.org/issues/show_bug.cgi?id=53643
          Examples: tests/compound{4,5}.*.

        - NOSUGGEST flag: words signed with NOSUGGEST flag are not suggested.
          Proposed flag for vulgar and obscene words (OOo Issue #55498).
          Example: tests/nosuggest.*.
          Problem reported by bobharvey at OOo:
          http://qa.openoffice.org/issues/show_bug.cgi?id=55498

        - KEEPCASE flag: Forbid capitalized and uppercased forms of words
          signed with KEEPCASE flags. Useful for special ortographies
          (measurements and currency often keep their case in uppercased
          texts) and other writing systems (eg. keeping lower case of IPA
          characters).

        - CHECKCOMPOUNDCASE: Forbid upper case characters at word bound in
compounds.
          Examples: tests/checkcompoundcase* and tests/germancompounding.*

        - FLAG UTF-8: New flag type: Unicode character encoded with UTF-8.
          Example: tests/flagutf8.*.
          Rationale: Unicode character type can be more readable
          (in a Unicode text editor) than `long' or `num' flag type.

bug fixes:
        * src/hunspell/hunspell.cxx: accept numbers and numbers with separators
(i53643)
          Bug reported by skelet at OOo:
          http://qa.openoffice.org/issues/show_bug.cgi?id=53643

        * src/hunspell/csutil.cxx: fix casing data in ISO 8859-13 character table.

        * src/hunspell/csutil.cxx: add ISO-8859-15 character encoding (i54980)
          Rationale: ISO-8859-15 is the default encoding of the French
OpenOffice.org
          dictionary. ISO-8859-15 is a modified version of ISO-8859-1
          (latin-1) character encoding with French oe ligatures and euro
          symbol. Problem reported by cbrunet at OOo in OOo Issue 54980:
          http://qa.openoffice.org/issues/show_bug.cgi?id=54980

        * src/hunspell/affixmgr.cxx: fix zero-byte malloc after a bad affix
header.
          Patch by Harri Pitk?nen.

        * src/hunspell/suggestmgr.cxx: fix bad NEEDAFFIX word suggestion
          in ngram suggestions. Reported by Daniel Naber and Friedel Wolff.

        * src/hunspell/hashmgr.cxx: fix bad white space checking in affix files.
          src/hunspell/{csutil,affixmgr}.cxx: add other white space separators.
          Problems with tabulators reported by Frederik Fouvry.

        * src/hunspell/*: replace system-dependent <license.*> #include
          parameters with quoted ones. Problem reported by Dafydd Jones.

        * src/hunspell/hunspell.cxx: fix missing morphological analysis of dot(s)
          Reported by Tr?n Viktor.

changes:
        * src/hunspell/affixmgr.cxx: rename PSEUDOROOT to NEEDAFFIX.
          Suggested by Bram Moolenaar.

        * src/hunspell/suggestmgr.hxx: Increase default maximum of
          ngram suggestions (3->5). Suggested by Kevin Hendricks.

        * src/hunspell/htypes.hxx: Increase MAXDELEN for long affix flags.

        * src/hunspell/suggestmgr.cxx: modify (perhaps fix) Unicode map
suggestion.
          tests/maputf test fail on ARM platform reported by Rene Engelhard.

        * src/hunspell/{affentry.cxx,atypes.hxx}: remove [PREFIX] and
          MISSING_DESCRIPTION messages from morphological analysis.
          Problems reported by Tr&#258;&#322;n Viktor.

        * tests/germancompounding.{aff,good}: Add "Computer-Arbeit" test word.
          Suggested by Daniel Naber.

        * doc/man/hunspell.4: Proof-reading patch by Goldman Eleon?ra

        * doc/man/hunspell.4: Fix bad affix example (replace `move' with
`work').
          Bug reported by Frederik Fouvry.

        * tests/*: new test files:
          affixes.*: simple affix compression example from Hunspell 4 manual
page
          checkcompoundcase.*, checkcompoundcase2.*, checkcompoundcaseutf.*
          compound.*, compound2.*, compound3.*, compound4.*, compound5.*
          compoundflag.* (former compound.*)
          flagutf8.*: test for FLAG UTF-8
          germancompounding.*: simplification with CHECKCOMPOUNDCASE.
          germancompoundingold.* (former germancompounding.*)
          i53643.*: check numbers with separators
          i54980.*: ISO8859-15 test
          keepcase.*: test for KEEPCASE
          needaffix*.* (former pseudoroot*.* tests)
          nosuggest.*: test for NOSUGGEST



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
> Thanks for the strict Debian policy, Hunspell 1.1.2 has been
>completed:

Dmitri Gabinski (muttering into his beard): never say "completed"
until you have it compiled for Windows.
   
 
   
---
????? ??????? ??????????? ????????? ???! http://shop.tut.by

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Andras Timar
Dmitri Gabinski ?rta:
>> Thanks for the strict Debian policy, Hunspell 1.1.2 has been completed:
>
>
> Dmitri Gabinski (muttering into his beard): never say "completed" until
> you have it compiled for Windows.
>    
I will build the Windows binary tonight. However, if you look at the
changelog, you can realize that these bugfixes have no effect on the
Windows platform. IMHO from the Windows point of view 1.1.2 release is
virtually identical to 1.1.1.

Cheers,
Andras

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
> I will build the Windows binary tonight.

J�l van :-)

> However, if you look at the
> changelog, you can realize that these bugfixes have no effect on the
> Windows platform. IMHO from the Windows point of view 1.1.2 release
>is
> virtually identical to 1.1.1.

Anyway, if you test something (and HunSpell still needs testing)
you've got to have the latest release, otherwise your bug reports
don't have much value (I've found one more thing to report in 1.1.1,
but I'd like to confirm it with 1.1.2).

Best regards,

Dmitri Gabinski
   
 
   
---
?????? ??? ?????? ????????? ?? ??????? ????????????, ???????? ?
??????? ???????. ??????????? ?? http://www.unitex.by/credit.php

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

nemeth-2
In reply to this post by Andras Timar
Quoting T?m?r Andr?s <[hidden email]>:

> Dmitri Gabinski ?rta:
> >> Thanks for the strict Debian policy, Hunspell 1.1.2 has been completed:
> >
> >
> > Dmitri Gabinski (muttering into his beard): never say "completed" until
> > you have it compiled for Windows.
> >
> I will build the Windows binary tonight. However, if you look at the
> changelog, you can realize that these bugfixes have no effect on the
> Windows platform. IMHO from the Windows point of view 1.1.2 release is
> virtually identical to 1.1.1.

Hi,

There are two fixes that relevant also on Windows, but only
for dictionary developers. Now Hunspell suggests ONLYINCOMPOUND words only
in compounds, and the backtracking works in the COMPOUND patterns:

--------compound6.aff--------
COMPOUNDMIN 1
COMPOUND 2
COMPOUND A*A
COMPOUND A*AAB*BBBC*C
--------compound6.dic--------
3
a/A
b/B
c/C

--------compound6.good--------
aa
aaaaaa
aabbbc
aaaaabbbbbbcccccc
--------compound6.wrong--------
abc
abbbbbccccccc
aabbccccccc
aabbbbbbb

Thanks for the Windows build!

Best regards,

Laci


>
> Cheers,
> Andras
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Rene Engelhard-7
In reply to this post by nemeth-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

[hidden email] wrote:
>         * src/hunspell/affixmgr.*: fix Unicode MAP errors (sorted only n-1
>           characters instead of n ones in UTF-16 MAP character lists).
>           Bug reported by Rene Engelhard.
>
>         * src/hunspell/affixmgr.*: fix infinite COMPOUND matching (default char
>           type is unsigned on PowerPC, s390 and ARM platforms and it will never
>           be negative). Bug reported by Rene Engelhard.
[...]
>         * configure.ac, tests/automake.am: set platform specific XFAIL test
>           (flagutf8.test on ARM platform)

Thanks. arm does still fail on maputf, though but as arm never built
sucessfully (build defined as "build including make check") this is not release-critical
in Debian for now.
But it of course should be fixed at some time :)

Regards,

Rene
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDdOCn+FmQsCSK63MRAnitAJ0W6NmtW4iFERrzXJiFceGqF9u+eQCcDsLE
Ef1uat4ae5MTfNiq+PxS6bc=
=as/j
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

nemeth-2
In reply to this post by Дмитрий Габинский
Hi,

Quoting Dmitri Gabinski <[hidden email]>:

> > I will build the Windows binary tonight.

Here: https://sourceforge.net/project/showfiles.php?group_id=143754

Thank you, Andr?s!

Regards,

Laci


>
> Jól van :-)
>
> > However, if you look at the
> > changelog, you can realize that these bugfixes have no effect on the
> > Windows platform. IMHO from the Windows point of view 1.1.2 release
> >is
> > virtually identical to 1.1.1.
>
> Anyway, if you test something (and HunSpell still needs testing)
> you've got to have the latest release, otherwise your bug reports
> don't have much value (I've found one more thing to report in 1.1.1,
> but I'd like to confirm it with 1.1.2).
>
> Best regards,
>
> Dmitri Gabinski
>
>
>
> ---
> ?&#65533;?&#65533;????&#65533; ??? ?????&#65533;?&#65533;
??&#65533;??&#65533;???&#65533;?? ?? ????&#65533;???&#65533;
> ?????&#65533;?&#65533;?&#65533;??&#65533;???,
?&#65533;??&#65533;?&#65533;???? ?
> ??&#65533;?&#65533;???? ?&#65533;??&#65533;????.
?&#65533;???&#65533;?????&#65533;?&#65533;? ??
> http://www.unitex.by/credit.php
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
> Thank you, Andr�s!

 From me too!

And now the promised bug report (I'm gonna make a report to sf.net,
but, well, later):
Again, there's a problem about upper/lowercase letter handling for
Russian/Belarusian (koi-8/cp1251).

Suppose, I want to write ?????. ???? or ?????. ????
(Russian/Belarusian respectively, common abbreviations meaning ?US
dollars?). If I forget to press Caps Lock, I get respectively ?????.
???? / ?????. ???? after the autocorrect function captalizes the first
letter. HunSpell identifies ????? / ????? as mistakes, but on
right-click suggests anything but ????? / ?????, in spite of those
abbreviations being present in the repsective dictionaries.

Best regards,

Dmitri Gabinski
   
   
   
---
?????? ?????? ??????????? ??????? ? ?????? - ???? "???" ? ?????? ????
?? ???????? ??????. ???????? ????? ?? 8000. ?? ????????? ?? ??????:
?????, ??.???????????????, 3 (??????????? ??? ????????)
???? "???", ?.768-90-73, e-mail: [hidden email], http://www.cafedom.by

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

nemeth-2
Hi Dmitri,

I cannot reproduce your bug with ru_RU dictionary with KOI-8
encoding. It works fine: http://hunspell.sourceforge.net/dmitri.png

BTW. Suggesting upper case equivalent is a Hunspell improvement implemented
with an ngram suggestion extension. Ngram suggestion is resource critical,
therefore Myspell and Hunspell search only ngram suggestions, if there
is no other (non ngram) suggestion.

Perhaps it is a Windows-1251 character conversion table error
in the OpenOffice.org source. I have just fixed the bad ISO-8859-13 (latin-7)
character table in Hunspell 1.1.2 (it came from OOo CVS).

Best regards,

Laci


Quoting Dmitri Gabinski <[hidden email]>:

> > Thank you, András!
>
>  From me too!
>
> And now the promised bug report (I'm gonna make a report to sf.net,
> but, well, later):
> Again, there's a problem about upper/lowercase letter handling for
> Russian/Belarusian (koi-8/cp1251).
>
> Suppose, I want to write ?&#65533;&#65533;????.
???&#65533;?&#65533;&#65533; or ?&#65533;&#65533;????.
?&#65533;??&#65533;?&#65533;&#65533;
> (Russian/Belarusian respectively, common abbreviations meaning
?&#65533;&#65533;US
> dollars?&#65533;&#65533;). If I forget to press Caps Lock, I get respectively
?&#65533;&#65533;????.
> ??&#65533;??&#65533;&#65533; / ?&#65533;&#65533;????.
?&#65533;?&#65533;??&#65533;&#65533; after the autocorrect function captalizes
> the first
> letter. HunSpell identifies ?&#65533;&#65533;??&#65533;??&#65533;&#65533; /
?&#65533;&#65533;?&#65533;?&#65533;??&#65533;&#65533; as mistakes, but on
> right-click suggests anything but
?&#65533;&#65533;???&#65533;?&#65533;&#65533; /
?&#65533;&#65533;?&#65533;??&#65533;?&#65533;&#65533;, in spite of

> those
> abbreviations being present in the repsective dictionaries.
>
> Best regards,
>
> Dmitri Gabinski
>
>
>
> ---
> ???&#65533;??&#65533;?&#65533; ???&#65533;?&#65533;??
???&#65533;???&#65533;?&#65533;??&#65533;?&#65533;?
?&#65533;????&#65533;?? ?
> ?&#65533;????? - ???&#65533;? "?&#65533;??" ? ?????? ????
> ?? ?????&#65533;???&#65533; ??????.
?&#65533;????&#65533;??? ?????&#65533; ??&#65533; 8000.
> ?&#65533;?&#65533; ???&#65533;?????&#65533;?&#65533; ??
???&#65533;??&#65533;?&#65533;:
> ?&#65533;???&#65533;?,
?&#65533;?.?&#65533;?&#65533;??&#65533;????&#65533;????&#65533;???&#65533;,
3 (????&#65533;?&#65533;???&#65533;??&#65533;?
> ??? ??&#65533;??&#65533;??&#65533;??)
> ???&#65533;? "?&#65533;??", ?&#65533;.768-90-73, e-mail: [hidden email],
> http://www.cafedom.by
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
Hi, Laci!

> I cannot reproduce your bug with ru_RU dictionary with KOI-8
> encoding. It works fine: http://hunspell.sourceforge.net/dmitri.png

Well, I, however, can :-( :

http://img483.imageshack.us/img483/2705/usa2jg.png

But I use ru_RU_yo and I'm under Windows. Can any of those factors
count?

Best regards,

Dmitri Gabinski
   
   
   
---
?????? ?????? ??????????? ??????? ? ?????? - ???? "???" ? ?????? ???? ??
???????? ??????. ???????? ????? ?? 8000. ?? ????????? ?? ??????: ?????,
??.??????????????? 3 (??????????? ??? ????????) ???? "???", ?.768-90-73,
e-mail: [hidden email], http://www.cafedom.by

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
In reply to this post by nemeth-2
Just to add: I've discovered one strange and a bit funny thing with
Belarusian: while ??? is not suggested for ????, ????? IS
suggested for ?????!

http://img496.imageshack.us/img496/3052/usa23fr.png

http://img478.imageshack.us/img478/6914/usa37gc.png

Is HunSpell USA-phobic? ;-)

Best regards,

Dmitri Gabinski
   
   
   
---
?????? ?????? ??????????? ??????? ? ?????? - ???? "???" ? ?????? ???? ??
???????? ??????. ???????? ????? ?? 8000. ?? ????????? ?? ??????: ?????,
??.??????????????? 3 (??????????? ??? ????????) ???? "???", ?.768-90-73,
e-mail: [hidden email], http://www.cafedom.by

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
In reply to this post by nemeth-2
> I cannot reproduce your bug with ru_RU dictionary with KOI-8
> encoding. It works fine: http://hunspell.sourceforge.net/dmitri.png

Sorry for floding the list with messages, but I've also decided to try
out ru_RU dictionary, and the result was absolutely the same as for
ru_RU_yo ? I've decided not to make a screenshot. Does this mean, that
the Windows implementation is different from Linux? This is, probably,
a question to Andras?

Best regards,

Dmitri Gabinski
   
   
   
---
?????? ?????? ??????????? ??????? ? ?????? - ???? "???" ? ?????? ???? ??
???????? ??????. ???????? ????? ?? 8000. ?? ????????? ?? ??????: ?????,
??.??????????????? 3 (??????????? ??? ????????) ???? "???", ?.768-90-73,
e-mail: [hidden email], http://www.cafedom.by

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Andras Timar
Dmitri Gabinski ?rta:
> Sorry for floding the list with messages, but I've also decided to try
> out ru_RU dictionary, and the result was absolutely the same as for
> ru_RU_yo ? I've decided not to make a screenshot. Does this mean, that
> the Windows implementation is different from Linux? This is, probably, a
> question to Andras...

I simply recompile the source and I do not add anything to it. I am not
aware of different implementation on Windows. If I do not forget, I'll
check your problem on my Windows box tonight. Can you send me your
dictionaries or a link to them in a private mail?

Cheers,
Andras

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Andras Timar
Dmitri Gabinski �rta:
>
> So, here are the dictionaries. The ru_RU is just what I downloaded from
> the OOo's site, ru_RU_yo is what I use with my additions and be_BY (for
> Belarusian) is my own work, still in progress ? you're among the first
> to use it :-)
>

1. English OpenOffice.org 2.0 on Windows with Hunspell 1.1.2 UNO
component and ru_RU_yo - same resultt as yours.
2. Hungarian OpenOffice.org 2.0 on Windows with built-in Hunspell 1.1.0
and  ru_RU_yo - same result as yours.
3. Hungarian OpenOffice.org m139 on Linux with built-in Hunspell 1.1.2
and ru_RU_yo - same result as yours. (!)
4. Hungarian OpenOffice.org m139 on Linux with Hunspell 1.1.2 UNO
component and ru_RU_yo - same result as yours. (!)

This means in my interpretation, that this is not a difference between
Linux and Windows. I also excluded the case, if I had made a mistake
building OOo or hunspell, because in case 4 I used the binary that Laci
built.

Cheers,
Andras

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

Дмитрий Габинский
T�m�r Andr�s <[hidden email]> ?????(?):

> This means in my interpretation, that this is not a difference
>between
> Linux and Windows.

That sound logical. But why then such a difference with Laci?

Best regards,

Dmitri Gabinski
   
   
   
---
?????? ?????? ??????????? ??????? ? ?????? - ???? "???" ? ?????? ???? ??
???????? ??????. ???????? ????? ?? 8000. ?? ????????? ?? ??????: ?????,
??.??????????????? 3 (??????????? ??? ????????) ???? "???", ?.768-90-73,
e-mail: [hidden email], http://www.cafedom.by

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lingu-dev] Hunspell 1.1.2

nemeth-2
In reply to this post by Rene Engelhard-7
Hi,

Quoting Rene Engelhard <[hidden email]>:

> Thanks. arm does still fail on maputf, though but as arm never built
> sucessfully (build defined as "build including make check") this is not
> release-critical
> in Debian for now.

Good news. Thanks for the test!

> But it of course should be fixed at some time :)

I agree, I will fix it.

Regards

Laci


>
> Regards,
>
> Rene
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFDdOCn+FmQsCSK63MRAnitAJ0W6NmtW4iFERrzXJiFceGqF9u+eQCcDsLE
> Ef1uat4ae5MTfNiq+PxS6bc=
> =as/j
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]