Bug#859760: marked as done (Can't read CJK in tables)

Fri Jun 2 08:45:14 UTC 2017

Your message dated Fri, 2 Jun 2017 10:40:47 +0200
with message-id <93f5c26a-b7db-8d19-8a49-5425ae28241d at xs4all.nl>
and subject line Re: Bug#859760: Can't read CJK in tables
has caused the Debian Bug report #859760,
regarding Can't read CJK in tables
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)

-- 
859760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859760
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?B?56mN5Li55bC8?= Dan Jacobson <jidanni at jidanni.org>
Subject: Can't read CJK in tables
Date: Fri, 07 Apr 2017 13:05:45 +0800
Size: 41928
URL: <http://lists.alioth.debian.org/pipermail/pkg-grass-devel/attachments/20170602/be001c4c/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Sebastiaan Couwenberg <sebastic at xs4all.nl>
Subject: Re: Bug#859760: Can't read CJK in tables
Date: Fri, 2 Jun 2017 10:40:47 +0200
Size: 2368
URL: <http://lists.alioth.debian.org/pipermail/pkg-grass-devel/attachments/20170602/be001c4c/attachment-0003.mht>