tags 514963 fixed-upstream
thanks

On Thu, Feb 12, 2009 at 12:57:10PM +0100, Michal Čihař wrote:
> Dne Thu, 12 Feb 2009 11:43:42 +0000
> Colin Watson <cjwat...@debian.org> napsal(a):
> > position 325 isn't representable in ISO-8859-2. Unfortunately, manconv
> > isn't currently smart enough to distinguish between "conversion failed
> > because this isn't valid UTF-8" and "conversion failed because this bit
> > of UTF-8 isn't available in the target encoding", and therefore it falls
> > back to recoding from ISO-8859-2 to ISO-8859-2 (i.e. a no-op) and then
> > you see the mess when it tries to interpret UTF-8 as if it were
> > ISO-8859-2.
> > 
> > I think it might be possible to fix this, albeit more slowly, by
> > recoding the page to UCS-4, which should always succeed as long as the
> > text matches the input encoding being tried, and then recoding from
> > there to ISO-8859-2 and just throwing away characters that don't fit.
> > Alternatively, by the time we've done that we might have a groff that
> > supports UTF-8 input!
> 
> Yes, that would be great.

Although we now have groff 1.20.1 in unstable so you should no longer
notice the effects of this bug, I've fixed it anyway for man-db 2.5.6.

Tue Aug 18 09:47:50 BST 2009  Colin Watson  <cjwat...@debian.org>

        * src/manconv.c (try_iconv): Convert text to UTF-8 and then (if
          necessary) to the target encoding. This allows us to distinguish
          between "text not in input encoding" and "characters not
          representable in output encoding" (Debian bug #514963).
        * src/tests/manconv-2: Add test for this and some other possible
          encoding-handling bugs in manconv.
        * src/tests/Makefile.am (TESTS): Add manconv-2.
        * NEWS: Document this.

Thanks for your report,

-- 
Colin Watson                                       [cjwat...@debian.org]



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to