Punctuation handling inconsistent between file types

[eb1]

Describe the bug
Noticed this while looking at imported USFM / AI XML docs. It appears that the import and handling of punctuation is not entirely consistent between file types, and doesn't really match what AI XML does:

• For Text, USX, and USFM files all preceding / following punctuation is removed from the source and placed in prepunct / follpunct DB fields
• For AI XML, AIM currently pulls out the k sourcephrase field, which kind-of strips the punctuation from the source. This causes some weirdness when colon characters are encountered, for example. If imported file type was XML, the word ending with a colon is displayed with the text differences color (e.g., dark green) -- even if the words are the same in source and target.

This should be modified so that all the files types handle punctuation consistently. I would vote that the punctuation not be stripped from the source field in the database, so that the source matches the s field in the AI XML file. The handling can then be consistent in AIM's UI, to strip out the punctuation when the user sets the focus on the field.

[eb1]

Marking issue as resolved:
Tested with Text, XML, USX, and USFM imported documents. All now are consistent in how they handle punctuation during import and adaptation.