--===============1021900112==
Content-Type: multipart/signed;
boundary="nextPart2146140.YM8c0WVz49";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

Sebastian Trueg wrote:
>my question is how I can detect if there are such filenames that could
> cause problems (in my case with mkisofs and joliet).


I saw the bug reports in question. We got Trolltech to handle invalid=20
UTF-8 sequences back in the day so that we could handle files properly=20
with wrong names.

When we do QFile::decodeName on one such file, the resulting QString=20
contains some private characters that have no meaning outside Qt.

However, the problem you describe is clearly a system misconfiguration.=20
The user should fix his file names instead.

=2D-=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358

5. Swa he g=C3=A9anhwearf t=C3=B3 timbran, and hwonne he c=C3=B3m, l=C3=A1!=
Unix cw=C3=A6=C3=B0 "Hello,=20
World". =C7=BCfre =C7=BDghwilc w=C3=A6s gl=C3=A6d and seo woruld w=C3=A6s f=
r=C3=A9o.

--nextPart2146140.YM8c0WVz49
Content-Type: application/pgp-signature

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

iD8DBQBDmludM/XwBW70U1gRAhwpAJ0YibV567nXwoU5bKKbzzHyw9aE3QCfUyjL
ZcWp+4u1rfjV4L2l7fwx+CY=
=oT9c
-----END PGP SIGNATURE-----

--nextPart2146140.YM8c0WVz49--

--===============1021900112==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


--===============1021900112==--