Re: Exe Naming on Windows

Hm, this for sure makes sense. During the last months we had a poll 
whether to drop or keep Ansi support and there was at least one user 
with Windows 98 so we decided to keep it.

WinMerge for example uses the names "WinMerge.exe" (Ansi) and 
"WinMergeU.exe" (Unicode). At least for the last versions I recall. With 
these names its not easier to chose the "default" version. Probably the 
one without the suffix (which is wrong on 99% of the Windows 
installations today).

But the concern makes sense. The Unicode build will be "rapidsvn.exe" 
and the Ansi build "rapidsvn_ansi.exe":
http://rapidsvn.tigris.org/issues/show_bug.cgi?id=665

Alex


Andrew Powell schrieb:
> Hello All,
> 
> 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.
> 
> Thanks,
> Andrew
> 
> ------------------------------------------------------
> http://rapidsvn.tigris.org/ds/viewMessage.do?dsForumId=671&dsMessageId=2376286
> 
> To unsubscribe from this discussion, e-mail: [[email protected]].

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

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