Bug#909577: hunspell-bg: Upgrade to fix encoding problem

To: Pander <pander@users.sourceforge.net>, 909577@bugs.debian.org
Cc: control@bugs.debian.org
Subject: Bug#909577: hunspell-bg: Upgrade to fix encoding problem
From: Rene Engelhard <rene@debian.org>
Date: Fri, 28 Sep 2018 23:33:01 +0200
Message-id: <[🔎] 20180928213301.GB28356@rene-engelhard.de>
Reply-to: Rene Engelhard <rene@debian.org>, 909577@bugs.debian.org
In-reply-to: <[🔎] 153788602055.13023.6199005217006088936.reportbug@rudra>
References: <[🔎] 153788602055.13023.6199005217006088936.reportbug@rudra> <[🔎] 153788602055.13023.6199005217006088936.reportbug@rudra>

tag 909577 + moreinfo
thanks

Hi,

On Tue, Sep 25, 2018 at 04:33:40PM +0200, Pander wrote:
> Please, upgrade in order to fix an encoding problem, the incorrect
> encoding name was used. This has been fixed upstream.

And you are reporting this against 5.2.5 which is in stable. Of course
this fix didn't end up there since it it isn't critical. Or is it?

> See also:
> https://sourceforge.net/p/bgoffice/bugs/6/
> https://bugs.documentfoundation.org/show_bug.cgi?id=117392

That was abandoned? Because "UTF-8 works now".

So what is the actual, still existing (in 6.1.1/.2) problem?

Regards,

Rene

Reply to:

Follow-Ups:
- Processed: Re: Bug#909577: hunspell-bg: Upgrade to fix encoding problem
  - From: "Debian Bug Tracking System" <owner@bugs.debian.org>
- Bug#909577: hunspell-bg: Upgrade to fix encoding problem
  - From: Mattia Rizzolo <mattia@debian.org>

References:
- Bug#909577: hunspell-bg: Upgrade to fix encoding problem
  - From: Pander <pander@users.sourceforge.net>

Prev by Date: Processed: Re: Bug#909577: hunspell-bg: Upgrade to fix encoding problem
Next by Date: Bug#909577: hunspell-bg: Upgrade to fix encoding problem
Previous by thread: Bug#909577: hunspell-bg: Upgrade to fix encoding problem
Next by thread: Processed: Re: Bug#909577: hunspell-bg: Upgrade to fix encoding problem
Index(es):
- Date
- Thread