> I'm a new user to TortoiseSVN and I'm using it with TestComplete (automation
> tool similar to HP QTP). The script files are *.sj but are just plain text files.
> TortoiseSVN was treating them as binary so when I created a package, it
> wouldn't report the diff. (I still don't understand that since I can see diffs from
> the Commit dialog so maybe I'm just missing something obvious?) So... to
> attempt to remedy this, I changed the mime-type (of every file individually,
> ugh!) to text, created a new patch with some simple changes, and now I can
> see the diff (kinda) but every other character is some NUL (?) character which
> makes it impossible to read.
> I can open the *.sj files with Windows Notepad so I know they are text of some
> flavor. Maybe they are encoded a certain way and that's causing the issue? I'm
> not sure how to proceed.
> I've attached a sample *.sj file and a screenshot of the patch diff so you can see
> the issue.
> Here are my questions:
> 1. How do I solve the NUL character in the patch diff issue?
> 2. How can I set up TortoiseSVN so that all *.sj files are treated as text mime-
> type (or whatever is needed so that I can view patch diffs) automatically?
We have a similar issue with generate SQL scripts from SQL Server Management studio. I assume the files are UTF-16 (Unicode). If you can have the tool create UTF-8 or ANSI encoded text files they should work much better.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-29 17:11:10 CEST