CDATA sections in Memsource XLIFF

Ocelot seems to “break” content that Memsource puts into CDATA blocks by turning certain characters into their HTML entities. Now it seems that this is not a huge deal for Memsource (we cannot open the resulting XLIFF file in their desktop editor, but it imports OK into Memsource and so far we did not see any issues with this), but just to be on the safe side, would it be possible for Ocelot to ignore CDATA sections?