--===============7295174885999695091==
Content-type: multipart/signed; boundary=nextPart4671949.AVUBupnZkg;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart4671949.AVUBupnZkg
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Sunday 06 November 2011, Alexander Potashev wrote:
> Hi!
>=20
> This year "militsiya" in Russia was renamed to police, so was the
> "Day of militsiya". Now I can't decide what to do with
> plan1/holiday_ru_ru and plan2/holiday_ru_ru in
> kdepimlibs/kholidays/holidays/. Here are the options:
> 1. Simply change the name of the holiday. But then if you open a year
> before 2011 in the calendar, you'll still see the new name of the
> holiday.
> 2. The best thing to do would be, I think, to have 2 holidays: the
> first should appear only for the year 2010 and before, and the second
> one only for 2011 and later. But I'm afraid this behaviour of the
> calendar can't be currently defined in the file "holiday_ru_ru".
>=20
> I wanted to know how other translation teams deal with this, so I
> grepped all holiday definition files and I've found an ":: After
> 2005" line in holiday_se_sv. The people who wrote this file probably
> meant that some holidays only existed before 2005 and some other
> holidays appeared in 2005. But ":: " lines are just comments, so
> they won't make the calendar work differently, am I wrong?
>=20
> The holiday I'm talking about is currently defined in holiday_ru_ru
> as follows: "=D0=94=D0=B5=D0=BD=D1=8C =D0=BC=D0=B8=D0=BB=D0=B8=D1=86=D0=
=B8=D0=B8"
>  on november 10

I'd say just rename it. As far as I'm concerned, the holiday files=20
always reflect the current state of things. I don't think that it makes=20
sense to try being historically accurate.

In the German holiday file there's the "Tag der Einheit" (Day of=20
Reunification). Obviously, this holiday did not exist before the German=20
reunification. Still it is not marked with a starting year (and IMHO=20
this is perfectly alright).

Anyway, that's just my view on this.


Regards,
Ingo

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEABECAAYFAk62+IwACgkQGnR+RTDgudjGdQCfZ9NPwFLMmk1TarvTC/wJcqA7
HI8AoLVwEVCyl7Xt/3UIQ8Uzib7tygqI
=xfEB
-----END PGP SIGNATURE-----

--nextPart4671949.AVUBupnZkg--

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

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============7295174885999695091==--