Bug 288150

Summary:	Classification of France overseas departments and territories
Product:	[Applications] kdepimlibs	Reporter:	Pierre Buard <pierre+libre.kde>
Component:	kholidays	Assignee:	John Layt <jlayt>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	annma, kdepim-bugs
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pierre Buard 2011-12-03 17:51:19 UTC

Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

France overseas departments and territories are dependencies, not countries (at least for now). Yet, in the holidays listing, they appear as such, scattering them, instead of placing them under the French header.

Reproducible: Always

Steps to Reproduce:
Load the settings for any plasma clocks. In the Calendar setting, subsection Holidays, look for France and see it all alone.


Expected Results:  
They should be listed under France, just like Bavaria is under Germany or Catalonia under Spain.

Comment 1 John Layt 2012-01-03 22:27:13 UTC

We implement the ISO standard for country codes which classifies French overseas departments at both level 1 and level 2.  See http://en.wikipedia.org/wiki/ISO_3166-2:FR for more details.

We have previously added these files at level 1 at the request of local users.  We could either move them to the level 2 codes, or just group them in the gui as part of France.  However, I'm not sure how residents of the overseas territories will respond to this, and it also opens the question of whether we keep the separate locales for those territories too.  cc Anne-Marie for her opinion.

Comment 2 Denis Kurz 2016-09-24 20:55:31 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:04:24 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.