Bug 236311

Summary: Systemsettings Country/Region & Language won't accept custom date format
Product: [Applications] systemsettings Reporter: crptdngl71
Component: kcm_formatsAssignee: Sebastian Kügler <sebas>
Status: RESOLVED DUPLICATE    
Severity: normal CC: hein, jlayt, nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description crptdngl71 2010-05-04 13:34:32 UTC
Version:           1.0 (using 4.4.3 (KDE 4.4.3), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.33-3.slh.4-sidux-amd64

The settings for country/region & language won't accept a custom setting for date.

Steps to reproduce:

1.) Tab "Regionales" set to "Deutsch" (German),

2.) Tab "Zeit & Datum" (Time & Date): in the line "Datumsformat" (format of date): setting is this:

WOCHENTAG, tT. MONAT JJJJ

which results in :

Datum: Dienstag, 4. Mai 2010

in the bottom part of the settings page, which is fine.

BUT:
Now I want to change the format of the day, so it results in

Datum: Dienstag, 04. Mai 2010

(i.e. add a 0 to the date unless it consists of two digits anyway).

To do that, I have to change the tT. setting in the date line to TT. which works, as indicated in the resulting line again in the bottom of the form. But I cannot make KDE accept this setting, it alway is reset to the line described above.
I can add the "." after the day which was not there previous to my editing, and KDE accepts this dot. But I cannot change tT to TT and have a dot applied to it as KDE will not accept that.

If KDE lets me edit the line and let me add this extra dot after the WOCHENTAG, so why won't it let me add another dot to the TT date as well?
Comment 1 John Layt 2010-08-07 22:09:15 UTC
I suspect this is a problem in the translated strings which are used to convert to/from the Posix format strings, as this works for me using en_GB.  I'll try check this.
Comment 2 Nate Graham 2021-01-06 00:34:24 UTC

*** This bug has been marked as a duplicate of bug 340982 ***