--nextPart10872012.4Splpgez5h
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Jaros=C5=82aw Staniek wrote:
>qFatal() was raised because of unrecognizable character '\r'.
>These characters may usually come from macosx or win32 environments.
>Since macosx and win32 KDE developemnt became something real, there may
> exist (at least by accident) source files with '\r' character. My patch
> accepts them by removing before parsing, as C/C++ preprocessors do.
>
>Ok to commit?

Isn't it possible to condense \r\n into \n instead? I don't think simply=20
eating all \r is healthy.

Stray \r in the source code is certainly corrupted file.

BTW, doesn't Mac use \r alone as its line-breaking character? If so, maybe=
=20
tr/\r/\n/ is the way to go, since whitespaces are whitespaces anywhere.
=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

1. On frumscafte, hwonne time_t w=C3=A6s n=C3=A1ht, se scieppend =C3=BEone =
circolwyrde=20
wundorcr=C3=A6ftl=C3=ADge cennede and seo eor=C3=B0e w=C3=A6s idel and hit =
w=C3=A6s g=C3=B3d.

--nextPart10872012.4Splpgez5h
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCDI/QM/XwBW70U1gRAtwTAJ0eE6XnYigVvm9Ph3kWKR4Bzb8rVACaA+eM
vVj1tRu1wiRsziYee7zc/Fk=
=oiYj
-----END PGP SIGNATURE-----

--nextPart10872012.4Splpgez5h--