"Claus Hentschel" <[EMAIL PROTECTED]> writes:
| > | > ios::text? No. It is a non-standard flag.
| > | > ...
| > | > ios::binary otoh is a standard flag and should work everywhere.
| > |
| > | So there seems not to be another way then removong those trailing \r's
| the
| > | way I'v done. We do need that in all cases where text read from a
| (binary)
| > | opened file is presented as-is in a window.
| >
| > Then we should not open those files in binary mode.
|
| That isn't possible if the drive/directory is mounted in binary mode!!!
I'd like to put this down as a configuration problem of cygwin/win
drives/dirs etc.
If you manage to setup the sustemt the stdlibc++ does not work, we
should not cater for it.
IMHO of course.
| Mounting *all* drives/dirs in text mode does produce other problems because
| then (not only with Lyx) reading any (although non-text) file *always*
| causes a byte translation \n -> \n\r!
Only on binaries that open their filen in the wrong mode.
If you want to be portable to win you have to use the ios::binary when
not reading a text file (and I know that lyx does not do this as it
should)
--
Lgb
