From koffice-devel  Sat Apr 21 06:48:48 2007
From: Thomas Zander <zander () kde ! org>
Date: Sat, 21 Apr 2007 06:48:48 +0000
To: koffice-devel
Subject: Re: RFC: Db icons and mimetypes
Message-Id: <200704210848.48656.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=117713816821385
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0114634270=="

--===============0114634270==
Content-Type: multipart/signed;
  boundary="nextPart2706169.FeAnQ50EFd";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2706169.FeAnQ50EFd
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 20 April 2007 21:56, Jaroslaw Staniek wrote:
> I guess it's the other way around: anyone who introduces a new mimetype
> for a file format have to point to this fileformat being available in
> the wild.

The specification of what kind of file is expected to have the mimetype is=
=20
available. So its not hard to make a file that correctly should carry the=20
mimetype.

If you are saying that we still need an application to actually write it=20
before the mime type should be attached to such files, well sure. Thats=20
true. Similarly you could not use the png mimetype until there were=20
actual applications that created the pngs. :)

Then again, lets be prepared for when kexi can export the format or when=20
another app can read/write it.  Being prepared means having the mimetype=20
in kdelibs as well as the icon. (Both already in place).  Which means=20
nothing to be done anymore.

Cheers!
=2D-=20
Thomas Zander

--nextPart2706169.FeAnQ50EFd
Content-Type: application/pgp-signature

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

iD8DBQBGKbPQCojCW6H2z/QRAi6SAKC/8YpEvHuzkmebAWp1jzktOrBYwwCfa2hh
P9qumtt8iCKaLj9giqNXHdw=
=hFe5
-----END PGP SIGNATURE-----

--nextPart2706169.FeAnQ50EFd--

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

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============0114634270==--