As designed Unmodified phrases receive a database entry on language import

[vbresults]

Affected version

2.x

When a language is imported and the phrase matches the master language entry, it still creates a database entry and appears as customized after the import. Whether or not the option to export unmodified phrases was checked (client did it), I can't see when this behavior would be useful.

This is confusing in the UI, adds thousands of unnecessary entries to the database, probably slows down rebuilds, and complicated a plugin I made. The latter required a custom query to wipe the duplicates.

 

[Mike]

This is as expected. The presence of an entry in the XML file means that it has been customized (or is assumed to be customized). The choice to export unmodified phrases is primarily to give an option to do file-based translations (where you edit in the XML file directly rather than the web interface).