# HG changeset patch
# User Paul Aurich <paul@darkrain42.org>
# Date 1277832861 0
# Node ID ebc34634e592d3babf246b517fe133e15b008ce2
# Parent  317cbbf56c2f2ef0c6177a25f349de715a374826
certificate: Add helpful text to the 'not yet active' message.

A bad clock is going to be the issue in basically all these cases,
unless you're explicitly creating interesting certs.

diff -r 317cbbf56c2f -r ebc34634e592 libpurple/certificate.c
--- a/libpurple/certificate.c	Wed Jun 23 04:43:44 2010 +0000
+++ b/libpurple/certificate.c	Tue Jun 29 17:34:21 2010 +0000
@@ -99,7 +99,8 @@
 			         "that can verify it is currently trusted.");
 			break;
 		case PURPLE_CERTIFICATE_NOT_ACTIVATED:
-			return _("The certificate is not valid yet.");
+			return _("The certificate is not valid yet.  Check that your "
+			         "computer's date and time are accurate.");
 			break;
 		case PURPLE_CERTIFICATE_EXPIRED:
 			return _("The certificate has expired and should not be "