--===============2028795867==
Content-Type: multipart/signed;
  boundary="nextPart3870141.0pznEVCjiQ";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3870141.0pznEVCjiQ
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 12 December 2008 23:30:42 =C1kos Szederjei wrote:
> > > Again, my main problem is how to =A0presentation the information in
> > > acceptable way. Any ideas?
> >
> > Do you mean how to get this information known and understood? =A0I woul=
d be
> > happy to help with a section in http://userbase.kde.org/KOrganizer,
> > either on the main page or on a linked troubleshooting page - maybe Q &=
 A
> > format? explaining why it is problematic and suggesting the best way of
> > dealing with it, if you would be willing to give it the eye when I've
> > done it, and check that it is explained clearly.
> >
> > Would that help?
> >
> > Anne
>
> Sure, I gladly help. Except between the 20th and New Year I will be away,
> but otherwise no problem.
>
> I meant the Lotus like implementation. I think it is difficult to impleme=
nt
> in a smooth way, if there are several changes to a reoccuring event.

OK - I'll see what I can do and get back to you.

Anne

--nextPart3870141.0pznEVCjiQ
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iEYEABECAAYFAklDjMIACgkQbMErw/n0TZoJvQCghQckW+L5rEmirY2ijPT/DM3L
5kUAn0svVzAmALcXk0utzUG6NRpdz3ZL
=0VhH
-----END PGP SIGNATURE-----

--nextPart3870141.0pznEVCjiQ--

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

_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users

--===============2028795867==--