Well, I found the issue in my particular case:
A developer had saved a template .sql
file he was using for new scripts. This file, somehow, was saved with UCS-2
(or Unicode
) encoding. Whenever he added files, TortoiseSVN determined that it was a binary file. By switching the encoding to UTF-8
, the template and files derived from it are added correctly as text/plain
.
Additional Info (Edit)
I found what might have been the culprit. When generating some scripts using the GUI, SQL Server Management Studio writes them as Unicode
in the query window. If the file is saved, it will be saved as Unicode
as well. Interestingly enough, files opened via the File
>New
don't save like this. An issue was raised with Microsoft about this back in 2007 (found here), that apparently hasn't been resolved.