BTW, for *PORTABILITY* I choose 't' (text mode), so it works both for UNIXes and Windows, even MACs.

I don't want to do this:
fopen(...., 'wb')
if (strpos('win', strtolower(PHP_OS)) !== false) {
  $line_ending = "\r\n";
} else {
  $line_ending = "\n";
}

which is NOT PORTABLE AT ALL. Why do you suggest 'b' mode will be more portable? The documentation is weird, IMHO.

Please provide a complete test case; most of these so called bug reports are due to the person viewing the data using the wrong tools.

FYI: "text mode" is an evil invention that usually leads to trouble.  It is generally better for the programmer to be explicit with their line endings, as it leads to a lower WTF? factor.

Hi Mr. Furlong! Thanks for the feedback.

The test case is complete. And I'm viewing it using a hex editor (doesn't matter which). The "Hello\n" will output exactly 6 bytes, the Hello and the 0D (\r). It's a MAC document, as detected by a good text editor. If you try to output more lines, i.e., "Hello\nWorld", the text will get concatenated if you try to use Notepad. Viewing it in WordPad or any other good text editor works fine.

>FYI: "text mode" is an evil invention that usually leads to trouble.

I agree with you. But it doesn't solve the problem. As stated in my previous problem, I can write code which use explicit line endings, but that will require me to write "if" statements for who-knows-how-many platforms I will need to support. It's easier that way.

Do you know setlocale() ? Yeah, try EXPLICITLY specifying your locale-specific formats without using strftime()-s formats and/or setlocale(). Things like this IMHO should be handled at lower levels of abstraction. And even if not, the lower level library should give the programmer a choice, i.e.: "we recommend you NOT to use it but if you use it we guarantee it will work correctly". In this case 'wt' doesn't work correctly.

BTW I can even e-mail you the exact script, the exact generated file, and even my entire PHP installation if you want to. ;-)

BTW in case you're wondering I use the mbstring extension with UTF-8 internal encoding specified in php.ini... but it shouldn't matter, should it?

Please try using this CVS snapshot:

  http://snaps.php.net/php5-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5-win32-latest.zip

And yes, mbstring might be the one causing trouble. Always try disabling everything possible.

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".