MySQL Bugs: #306: Readme not readable on Windows

Bug #306	Readme not readable on Windows
Submitted:	17 Apr 2003 17:24	Modified:	28 Jul 2003 14:55
Reporter:	Marsh Ray	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	4.0.12	OS:	Windows (Windows)
Assigned to:	Greg Weir	CPU Architecture:	Any

Description:
Installed mysql-4.0.12-win on Win XP SP1.
File 'Readme' cannot be opened by shell because it has no extension.
Manually adding the extension '.txt' opens the file with Notepad, but the line delimiters are not CRLF as a Windows text file should be.
This is also a problem for 'docs\Copying'.
Delimiters were also incorrect for 'docs\manual.txt'.
There may be other text files that have this problem.
Thanks!

How to repeat:
1. Install mysql-4.0.12-win on any Windows OS.
2. Navigate to C:\mysql in Windows Explorer
3. Double-click on 'Readme'
4. Observe that Windows prompts you to search or select a program to open the file. Notice that it is unable to retain your selection.
5. Select 'Notepad' from the list.
6. Observe that file is unreadable due to line delimiter problems.

Suggested fix:
Implement a line delimiter conversion step for text files in Windows builds.
Ensure that text files end with '.txt' extension under Windows.

Instead of notepad.exe for to read those files,
the Windows offers the option to use Wordpad.exe
which is able to read them.

Sure _I_ know how to open the file on Windows. That doesn't change the fact that your Readme is not a valid Windows text file, so there's nothing "Bogus" about this bug report. These mistakes are the kind of thing that one sees in third-rate shareware packages that migraged from DOS to Windows.

While it is true that adding extensions to these files would help new users, it should be noted that MySQL did not migrate from DOS, but Solaris/*nix

This will be changed in all Windows releases after 4.0.14, including the addition of the .txt extension and conversion to CR/LF pairs.