[interchange] Fix for processing GDBM files while using UTF8

commit 46c876e72457c92d4a57b2ba9549b3f67cbfd3d6
Author: Gert van der Spoel <[email protected]>
Date:   Sun Mar 27 15:16:46 2011 +0200

    Fix for processing GDBM files while using UTF8
    
    It appears that utf8 filter should not be applied when creating GDBM
    files. This seems to cause a double encoding. Prerequisite is that
    the TXT file out of which the GDBM file is built is UTF8 encoded.
    
    But when working with UTF8 this should be the case else the TXT files
    are not able to be worked with with various languages.

 lib/Vend/Table/GDBM.pm |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)
---
diff --git a/lib/Vend/Table/GDBM.pm b/lib/Vend/Table/GDBM.pm
index 67a9fd2..fb82dbb 100644
--- a/lib/Vend/Table/GDBM.pm
+++ b/lib/Vend/Table/GDBM.pm
@@ -66,8 +66,6 @@ sub create {
 	my $dbm = tie(%$tie, 'GDBM_File', $filename, $flags, $File_permission_mode)
 		or die ::errmsg("%s %s: %s\n", ::errmsg("create"), $filename, $!);
 
-	apply_utf8_filters($dbm) if $config->{GDBM_ENABLE_UTF8};
-
 	$tie->{'c'} = join("\t", @$columns);
 
 	my $s = [