[prev in list] [next in list] [prev in thread] [next in thread] 

List:       interchange-users
Subject:    Re: [ic] vlink display of UTF8 characters
From:       Peter <peter () pajamian ! dhs ! org>
Date:       2016-08-16 11:29:06
Message-ID: 987c6c3d-3b27-ee6b-e317-1f3b373ad518 () pajamian ! dhs ! org
[Download RAW message or body]

On 16/08/16 20:34, Peter wrote:
> I'm definitely not going to commit this without a fair bit of further
> review, and I still would like to see patches for vlink.c and tlink.c.
> I have no idea how those would handle it.

Ok, I'm now finding there are places in the code that work with the
binmode and places that work without it.  For example:

[data userdb fname foo] ... returns data that is corrupt without the
binmode but works with the binmode line, but...

[value fname]

... returns data that works without the binmode but is corrupt with it.

At the end of the day it looks like some methods of importing data to IC
are encoding it and some are not.  If it gets encoded then it ends up
double-encoded (or something), unless the binmode line removes one of
the encodings.  To that end I'm abandoning the idea of putting binmode
in vlink and instead I've just written a simple filter that runs the
data through Encode::decode().  This seems to allow the wrong data to
display correctly without causing all sorts of other issues.


Peter

_______________________________________________
interchange-users mailing list
interchange-users@icdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchange-users
[prev in list] [next in list] [prev in thread] [next in thread]