This is a discussion on Re: utf8 encoding in source code - KDE ; --===============0002009981== Content-Type: multipart/signed; boundary="nextPart1684045.lV07MGJuZP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1684045.lV07MGJuZP Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Michael Pyne wrote: >As mentioned elsewhere, stuff like names in the comments could be in > utf-8. Remember that Doxygen docs are generated from ...
--===============0002009981==
Content-Type: multipart/signed;
boundary="nextPart1684045.lV07MGJuZP";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
--nextPart1684045.lV07MGJuZP
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Michael Pyne wrote:
>As mentioned elsewhere, stuff like names in the comments could be in
> utf-8.
Remember that Doxygen docs are generated from comments in source code, so=20
the comments should be in UTF-8.
=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.
--nextPart1684045.lV07MGJuZP
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQBDcsIDM/XwBW70U1gRAjMuAKCGNHIX392jK9HbfIBYm2ng1haU1QCgq7nu
G5rMCNXMlcCvE5aZ2SAHEcE=
=EtZ7
-----END PGP SIGNATURE-----
--nextPart1684045.lV07MGJuZP--
--===============0002009981==
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 <<
--===============0002009981==--