Description of problem:
When exporting TMX, I found an instance of a NUL character (\0) in one of our HTextFlowTargets. We need to fix our input validation in the client, in the server, and preferably in the database constraints to prevent this from happening again.
If we detect NUL in a user file, we should generate an error message which directs the user to the offending line.
select * from HTextFlow where content0 LIKE CONCAT("%", CHAR(0x00 using utf8), "%");
select * from HTextFlowTarget where content0 LIKE CONCAT("%", CHAR(0x00 using utf8), "%");
Set to low serverity as low occurance and easy user fix
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-337