From kde-core-devel Sat Nov 03 07:37:06 2001 From: Thomas Zander Date: Sat, 03 Nov 2001 07:37:06 +0000 To: kde-core-devel Subject: Re: registering KDE-specific MIME-Types with IANA? X-MARC-Message: https://marc.info/?l=kde-core-devel&m=100478317710491 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--C7zPtVaVf+AK4Oqc" --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 03, 2001 at 05:17:57AM +0000, Rik Hemsley wrote: > #if Marc Mutz > > While reading RFC's for KMime I came across the fact that x-* MIME-type= s=20 > > are deprecated (rfc2048 - MIME Part 4: Registration procedures).=20 > > Proprietary mime types should be registered under the vnd. tree. Should= =20 > > we try to collect all KDE-specific mime types under vnd.kde.*? >=20 > Seems like a good plan to me. Any drawbacks ? The only one I see is that koffice applications register the mime types ins= ide their document for embedded parts, so a backwards compatability has to be a= dded=20 (an .desktop file to the users installation) We saw this allready with KOffice files containing embedded KIllustrator fi= les refusing to open. But something that will be a more lasting problem is that newly created=20 documents with embedded parts (which have a new mime type) can not be opene= d=20 with old releases. Personally I don't think this is a big problem though, with the current rate of change (read: improvement :) it is justified to let people upgrade anywa= y. --=20 Thomas Zander zander@earthling.n= et The only thing worse than failure is the fear of trying something new --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7456iCojCW6H2z/QRAizNAKCiahd3XgVHxiMbNtl0c2gyrI6xHwCeICV1 lkKbafUwumgYktwn0LxmUSI= =dGV9 -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc--