[Issue 665] New - Windows: Drop suffix for unicode exe

http://rapidsvn.tigris.org/issues/show_bug.cgi?id=665
                 Issue #|665
                 Summary|Windows: Drop suffix for unicode exe
               Component|rapidsvn
                 Version|0.10
                Platform|PC
              OS/Version|Windows 2000
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|packages
             Assigned to|issues@rapidsvn
             Reported by|xelarellum






------- Additional comments from [email protected] Tue Jul 28 12:00:23 -0700 2009 -------
Andrew Powell questioned the sense of having "rapidsvn_ansi.exe" and
"rapidsvn_unicode.exe":
What was the reasoning behind the choice of the EXE file names on
windows? I ask this because I'm not aware of a Windows OS within the
last 10 years that doesn't support unicode. It would have made much
more logical sense to continue following the original naming structure
by naming the primary exe rapidsvn.exe as per usual, and naming the
specialized ansi executable as such (rapidsvn_ansi.exe). Additionally,
how are your basic users going to know which exe to run if they opt
out of creating the shortcuts during install?

Just looking for some clarity on this change. It seems a bit odd to
have two executable files which specify what each is for, neither
being the seemingly default exe.

Conclusion: we will drop the "_unicode" suffix for the Unicode build.

------------------------------------------------------
http://rapidsvn.tigris.org/ds/viewMessage.do?dsForumId=670&dsMessageId=2376362

To unsubscribe from this discussion, e-mail: [[email protected]].