Hi! We've been using a flat tab-separated text file for translations so far. Since we're expanding, we want to move to a database-based localization system. There are some problems, however. Thing is, we created a table for localization in MySQL and populated it with a mixture of latin1 and utf8-encoded strings from the current translation system. It had the needed fields. When interchange was configured to use it, it _completely changed the structure of the table_... The code field was limited to 16 characters -- a limitation not part of the flat text file and which caused some fields to be truncated. Furthermore, it seems that interchange also messed up the character set encodings of various fields. So, should we just keep on using the current system? Or is there a fix for this? Elver _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.