--===============0134349281==
Content-Type: multipart/signed;
  boundary="nextPart13059505.ILdWads8MN";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart13059505.ILdWads8MN
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

http://www.kdedevelopers.org/node/2492
  What KOffice has said in the past is that users should report any=20
problems in transferring documents so we can fix them. While this=20
sounds like a great way to find the problems the programmers missed,=20
its very time consuming since we first need to figure out if the file=20
was saved wrong, or if its opened incorrect. With some=20
misunderstandings over what the spec actually said thrown in every now=20
and then as well. Any typical document will usually use quite a lot of=20
features so it becomes even harder to figure out what is going wrong.

Bring in a testsuite. A long list of small documents each showing a=20
different feature in the spec so application developer can see which=20
feature they are not doing correctly and fix it in a next version.
http://testsuite.opendocumentfellowship.org/

=2D-=20
Thomas Zander

--nextPart13059505.ILdWads8MN
Content-Type: application/pgp-signature

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

iD8DBQBFRkH7CojCW6H2z/QRAj+qAKCRW0McwESKL8VJPi+mpF/fjbEf5gCgvdXf
wurehJaw5TEM0XGE2gd3Wgk=
=pad5
-----END PGP SIGNATURE-----

--nextPart13059505.ILdWads8MN--

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

____________________________________
koffice mailing list
koffice@kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice

--===============0134349281==--