Re: Bug#1028124: Bug#1028130: r-cran-hunspell: please don't use internal en_US and en_GB dictionaries
Ho,
Am 10. Januar 2023 09:27:16 MEZ schrieb Andreas Tille <andreas@an3as.eu>:
However, I get two failures
>> >when running its test suite:
>> >
>> >
>> >══ Failed tests ════════════════════════════════════════════════════════════════
>> >── Failure ('test-encodings.R:16'): Dictionaries are found ─────────────────────
>> >hunspell_info("en_US")$wordchars not equal to "’".
>> >1/1 mismatches
>> >x[1]: "0123456789’"
>> >y[1]: "’"
>>
>> Groan. Looks like it needs some specific stuff in the dictionaries it has which are now used from the system. I don't think it should not do that, can't the tests be adapted?
>
>Possibly. I'm fine with skipping these two tests for the moment.
>I'd assume that upstream will stumble upon this once the package
>itself is upgraded to hunspell 1.7.2.
I don't believe that failure is because of hunspell 1.7.2.. But related to the usage of other dictionaries... So as long as they ship internal dictionaries...
Then again noone expected the Korean failure(s) either...
Should be easy to cross check...
Regards
René
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Reply to: