Best practice to customize date/time format system-wide?Set custom locales in Gnome3 (on Fedora 20)Change a...
How were medieval castles built in swamps or marshes without draining them?
Why do proofs of Bernoulli's equation assume that forces on opposite ends point in different directions?
Handling Disruptive Student on the Autism Spectrum
Can a giant mushroom be used as a material to build watercraft or sailing ships?
Evaluated vs. unevaluated Association
"fF" letter combination seems to be typeset strangely or incorrectly
What are the occurences of total war in the Native Americans?
Prove your innocence
Talk interpreter
“T” in subscript in formulas
The Wires Underground
Does Yeshayahu 43:10b / 43:13a imply HaShem was created?
Round towards zero
How does encoder decoder network works?
Redacting URLs as an email-phishing preventative?
Add 2 new columns to existing dataframe using apply
Why did Khan ask Admiral James T. Kirk about Project Genesis?
Nothing like a good ol' game of ModTen
"There were either twelve sexes or none."
Prison offence - trespassing underwood fence
How much does Commander Data weigh?
Semantic difference between regular and irregular 'backen'
Is first Ubuntu user root?
Higman's lemma and a manuscript of Erdős and Rado
Best practice to customize date/time format system-wide?
Set custom locales in Gnome3 (on Fedora 20)Change a locale definition (as opposed to a locale setting)How do I find a locale which formats date and time the way I want?Change System Time/Datewho -b date format varies strangelyLinux ls wrong date formatLMDE2 / MATE locale charset inconsistencyHow to hack and modify a predefined date time format of KDE 5 that comes with Debian 9.2.1 Stretch?How do I find a locale which formats date and time the way I want?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'd like to customize exclusively the date and time format for my system, while sticking to the rest of the locale as is. I know that environment variable LC_TIME will make it possible to customize that aspect only by pointing to an alternate locale. Since I am using Linux (Ubuntu 14.04 to be precise), I want to use the format understood by localedef as input.
I have read the following three pieces of documentation:
- http://pubs.opengroup.org/onlinepubs/009696699/basedefs/xbd_chap07.html
- http://manpages.ubuntu.com/manpages/trusty/man1/localedef.1posix.html
- https://ccollins.wordpress.com/2009/01/06/how-to-change-date-formats-on-ubuntu/
The last one was particularly helpful.
Now, I only want to customize the section for LC_TIME and would like to inherit verything else.
So I copied en_US to a file named isodate in /usr/share/i18n/locales and adjusted the values I care about. After sifting through the documentation I decided also to replace all other section contents with a copy-keyword.
Question: It's not clear to me what method is supposed to be best practice. Does anyone know that (or even another alternative than those given by me)?
For example, since I care only about a few values (d_t_fmt, d_fmt, t_fmt, t_fmt_ampm, am_pm, date_fmt) it would be sweet to inherit all of en_US for LC_TIME and then merely overwrite those values with my ISO-like format (ISO 8601). However, the documentation about copy states (emphasis mine):
copy
Specify the name of an existing locale which shall be used as the definition of this category. If this keyword is specified, no other keyword shall be specified.
This means I cannot simply throw in a copy and then add more keywords.
Also, might it be legit to only define the LC_TIME section or will localedef outright refuse to compile that?
TL;DR
What is the best practice for customizing my date and time format settings, while sticking to the DRY-principle, i.e. without repeating stuff unnecessarily?
What I came up with so far:
escape_char /
comment_char %
LC_IDENTIFICATION
copy "en_US"
END LC_IDENTIFICATION
LC_CTYPE
copy "en_US"
END LC_CTYPE
LC_COLLATE
copy "en_US"
END LC_COLLATE
LC_MONETARY
copy "en_US"
END LC_MONETARY
LC_NUMERIC
copy "en_US"
END LC_NUMERIC
LC_TIME
abday "<U0053><U0075><U006E>";"<U004D><U006F><U006E>";/
"<U0054><U0075><U0065>";"<U0057><U0065><U0064>";/
"<U0054><U0068><U0075>";"<U0046><U0072><U0069>";/
"<U0053><U0061><U0074>"
day "<U0053><U0075><U006E><U0064><U0061><U0079>";/
"<U004D><U006F><U006E><U0064><U0061><U0079>";/
"<U0054><U0075><U0065><U0073><U0064><U0061><U0079>";/
"<U0057><U0065><U0064><U006E><U0065><U0073><U0064><U0061><U0079>";/
"<U0054><U0068><U0075><U0072><U0073><U0064><U0061><U0079>";/
"<U0046><U0072><U0069><U0064><U0061><U0079>";/
"<U0053><U0061><U0074><U0075><U0072><U0064><U0061><U0079>"
week 7;19971130;7
first_weekday 1
first_workday 2
abmon "<U004A><U0061><U006E>";"<U0046><U0065><U0062>";/
"<U004D><U0061><U0072>";"<U0041><U0070><U0072>";/
"<U004D><U0061><U0079>";"<U004A><U0075><U006E>";/
"<U004A><U0075><U006C>";"<U0041><U0075><U0067>";/
"<U0053><U0065><U0070>";"<U004F><U0063><U0074>";/
"<U004E><U006F><U0076>";"<U0044><U0065><U0063>"
mon "<U004A><U0061><U006E><U0075><U0061><U0072><U0079>";/
"<U0046><U0065><U0062><U0072><U0075><U0061><U0072><U0079>";/
"<U004D><U0061><U0072><U0063><U0068>";/
"<U0041><U0070><U0072><U0069><U006C>";/
"<U004D><U0061><U0079>";/
"<U004A><U0075><U006E><U0065>";/
"<U004A><U0075><U006C><U0079>";/
"<U0041><U0075><U0067><U0075><U0073><U0074>";/
"<U0053><U0065><U0070><U0074><U0065><U006D><U0062><U0065><U0072>";/
"<U004F><U0063><U0074><U006F><U0062><U0065><U0072>";/
"<U004E><U006F><U0076><U0065><U006D><U0062><U0065><U0072>";/
"<U0044><U0065><U0063><U0065><U006D><U0062><U0065><U0072>"
% Appropriate date and time representation (%c)
% "%Y-%m-%d %H:%M:%S"
d_t_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
% Appropriate date representation (%x)
% "%Y-%m-%d"
d_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064>"
%
% Appropriate time representation (%X)
% "%H:%M:%S"
t_fmt "<U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
t_fmt_ampm ""
%
am_pm "";""
%
% Appropriate date representation (date(1)) "%Y-%m-%d %H:%M:%S"
date_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
END LC_TIME
LC_MESSAGES
copy "en_US"
END LC_MESSAGES
LC_PAPER
copy "en_US"
END LC_PAPER
LC_NAME
copy "en_US"
END LC_NAME
LC_ADDRESS
copy "en_US"
END LC_ADDRESS
LC_TELEPHONE
copy "en_US"
END LC_TELEPHONE
LC_MEASUREMENT
copy "en_US"
END LC_MEASUREMENT
linux date locale
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
add a comment |
I'd like to customize exclusively the date and time format for my system, while sticking to the rest of the locale as is. I know that environment variable LC_TIME will make it possible to customize that aspect only by pointing to an alternate locale. Since I am using Linux (Ubuntu 14.04 to be precise), I want to use the format understood by localedef as input.
I have read the following three pieces of documentation:
- http://pubs.opengroup.org/onlinepubs/009696699/basedefs/xbd_chap07.html
- http://manpages.ubuntu.com/manpages/trusty/man1/localedef.1posix.html
- https://ccollins.wordpress.com/2009/01/06/how-to-change-date-formats-on-ubuntu/
The last one was particularly helpful.
Now, I only want to customize the section for LC_TIME and would like to inherit verything else.
So I copied en_US to a file named isodate in /usr/share/i18n/locales and adjusted the values I care about. After sifting through the documentation I decided also to replace all other section contents with a copy-keyword.
Question: It's not clear to me what method is supposed to be best practice. Does anyone know that (or even another alternative than those given by me)?
For example, since I care only about a few values (d_t_fmt, d_fmt, t_fmt, t_fmt_ampm, am_pm, date_fmt) it would be sweet to inherit all of en_US for LC_TIME and then merely overwrite those values with my ISO-like format (ISO 8601). However, the documentation about copy states (emphasis mine):
copy
Specify the name of an existing locale which shall be used as the definition of this category. If this keyword is specified, no other keyword shall be specified.
This means I cannot simply throw in a copy and then add more keywords.
Also, might it be legit to only define the LC_TIME section or will localedef outright refuse to compile that?
TL;DR
What is the best practice for customizing my date and time format settings, while sticking to the DRY-principle, i.e. without repeating stuff unnecessarily?
What I came up with so far:
escape_char /
comment_char %
LC_IDENTIFICATION
copy "en_US"
END LC_IDENTIFICATION
LC_CTYPE
copy "en_US"
END LC_CTYPE
LC_COLLATE
copy "en_US"
END LC_COLLATE
LC_MONETARY
copy "en_US"
END LC_MONETARY
LC_NUMERIC
copy "en_US"
END LC_NUMERIC
LC_TIME
abday "<U0053><U0075><U006E>";"<U004D><U006F><U006E>";/
"<U0054><U0075><U0065>";"<U0057><U0065><U0064>";/
"<U0054><U0068><U0075>";"<U0046><U0072><U0069>";/
"<U0053><U0061><U0074>"
day "<U0053><U0075><U006E><U0064><U0061><U0079>";/
"<U004D><U006F><U006E><U0064><U0061><U0079>";/
"<U0054><U0075><U0065><U0073><U0064><U0061><U0079>";/
"<U0057><U0065><U0064><U006E><U0065><U0073><U0064><U0061><U0079>";/
"<U0054><U0068><U0075><U0072><U0073><U0064><U0061><U0079>";/
"<U0046><U0072><U0069><U0064><U0061><U0079>";/
"<U0053><U0061><U0074><U0075><U0072><U0064><U0061><U0079>"
week 7;19971130;7
first_weekday 1
first_workday 2
abmon "<U004A><U0061><U006E>";"<U0046><U0065><U0062>";/
"<U004D><U0061><U0072>";"<U0041><U0070><U0072>";/
"<U004D><U0061><U0079>";"<U004A><U0075><U006E>";/
"<U004A><U0075><U006C>";"<U0041><U0075><U0067>";/
"<U0053><U0065><U0070>";"<U004F><U0063><U0074>";/
"<U004E><U006F><U0076>";"<U0044><U0065><U0063>"
mon "<U004A><U0061><U006E><U0075><U0061><U0072><U0079>";/
"<U0046><U0065><U0062><U0072><U0075><U0061><U0072><U0079>";/
"<U004D><U0061><U0072><U0063><U0068>";/
"<U0041><U0070><U0072><U0069><U006C>";/
"<U004D><U0061><U0079>";/
"<U004A><U0075><U006E><U0065>";/
"<U004A><U0075><U006C><U0079>";/
"<U0041><U0075><U0067><U0075><U0073><U0074>";/
"<U0053><U0065><U0070><U0074><U0065><U006D><U0062><U0065><U0072>";/
"<U004F><U0063><U0074><U006F><U0062><U0065><U0072>";/
"<U004E><U006F><U0076><U0065><U006D><U0062><U0065><U0072>";/
"<U0044><U0065><U0063><U0065><U006D><U0062><U0065><U0072>"
% Appropriate date and time representation (%c)
% "%Y-%m-%d %H:%M:%S"
d_t_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
% Appropriate date representation (%x)
% "%Y-%m-%d"
d_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064>"
%
% Appropriate time representation (%X)
% "%H:%M:%S"
t_fmt "<U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
t_fmt_ampm ""
%
am_pm "";""
%
% Appropriate date representation (date(1)) "%Y-%m-%d %H:%M:%S"
date_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
END LC_TIME
LC_MESSAGES
copy "en_US"
END LC_MESSAGES
LC_PAPER
copy "en_US"
END LC_PAPER
LC_NAME
copy "en_US"
END LC_NAME
LC_ADDRESS
copy "en_US"
END LC_ADDRESS
LC_TELEPHONE
copy "en_US"
END LC_TELEPHONE
LC_MEASUREMENT
copy "en_US"
END LC_MEASUREMENT
linux date locale
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
3
It's ok to only define one section and copy the other ones...
– don_crissti
May 17 '15 at 23:23
2
@K7AAY - that tag is completely irrelevant. There is absolutely nothing Ubuntu-specific here.
– don_crissti
Aug 21 '18 at 18:38
You might want to take a look at en_DK.UTF-8 :) I guess it's what you want.
– Pierre-Alain TORET
Oct 17 '18 at 10:07
add a comment |
I'd like to customize exclusively the date and time format for my system, while sticking to the rest of the locale as is. I know that environment variable LC_TIME will make it possible to customize that aspect only by pointing to an alternate locale. Since I am using Linux (Ubuntu 14.04 to be precise), I want to use the format understood by localedef as input.
I have read the following three pieces of documentation:
- http://pubs.opengroup.org/onlinepubs/009696699/basedefs/xbd_chap07.html
- http://manpages.ubuntu.com/manpages/trusty/man1/localedef.1posix.html
- https://ccollins.wordpress.com/2009/01/06/how-to-change-date-formats-on-ubuntu/
The last one was particularly helpful.
Now, I only want to customize the section for LC_TIME and would like to inherit verything else.
So I copied en_US to a file named isodate in /usr/share/i18n/locales and adjusted the values I care about. After sifting through the documentation I decided also to replace all other section contents with a copy-keyword.
Question: It's not clear to me what method is supposed to be best practice. Does anyone know that (or even another alternative than those given by me)?
For example, since I care only about a few values (d_t_fmt, d_fmt, t_fmt, t_fmt_ampm, am_pm, date_fmt) it would be sweet to inherit all of en_US for LC_TIME and then merely overwrite those values with my ISO-like format (ISO 8601). However, the documentation about copy states (emphasis mine):
copy
Specify the name of an existing locale which shall be used as the definition of this category. If this keyword is specified, no other keyword shall be specified.
This means I cannot simply throw in a copy and then add more keywords.
Also, might it be legit to only define the LC_TIME section or will localedef outright refuse to compile that?
TL;DR
What is the best practice for customizing my date and time format settings, while sticking to the DRY-principle, i.e. without repeating stuff unnecessarily?
What I came up with so far:
escape_char /
comment_char %
LC_IDENTIFICATION
copy "en_US"
END LC_IDENTIFICATION
LC_CTYPE
copy "en_US"
END LC_CTYPE
LC_COLLATE
copy "en_US"
END LC_COLLATE
LC_MONETARY
copy "en_US"
END LC_MONETARY
LC_NUMERIC
copy "en_US"
END LC_NUMERIC
LC_TIME
abday "<U0053><U0075><U006E>";"<U004D><U006F><U006E>";/
"<U0054><U0075><U0065>";"<U0057><U0065><U0064>";/
"<U0054><U0068><U0075>";"<U0046><U0072><U0069>";/
"<U0053><U0061><U0074>"
day "<U0053><U0075><U006E><U0064><U0061><U0079>";/
"<U004D><U006F><U006E><U0064><U0061><U0079>";/
"<U0054><U0075><U0065><U0073><U0064><U0061><U0079>";/
"<U0057><U0065><U0064><U006E><U0065><U0073><U0064><U0061><U0079>";/
"<U0054><U0068><U0075><U0072><U0073><U0064><U0061><U0079>";/
"<U0046><U0072><U0069><U0064><U0061><U0079>";/
"<U0053><U0061><U0074><U0075><U0072><U0064><U0061><U0079>"
week 7;19971130;7
first_weekday 1
first_workday 2
abmon "<U004A><U0061><U006E>";"<U0046><U0065><U0062>";/
"<U004D><U0061><U0072>";"<U0041><U0070><U0072>";/
"<U004D><U0061><U0079>";"<U004A><U0075><U006E>";/
"<U004A><U0075><U006C>";"<U0041><U0075><U0067>";/
"<U0053><U0065><U0070>";"<U004F><U0063><U0074>";/
"<U004E><U006F><U0076>";"<U0044><U0065><U0063>"
mon "<U004A><U0061><U006E><U0075><U0061><U0072><U0079>";/
"<U0046><U0065><U0062><U0072><U0075><U0061><U0072><U0079>";/
"<U004D><U0061><U0072><U0063><U0068>";/
"<U0041><U0070><U0072><U0069><U006C>";/
"<U004D><U0061><U0079>";/
"<U004A><U0075><U006E><U0065>";/
"<U004A><U0075><U006C><U0079>";/
"<U0041><U0075><U0067><U0075><U0073><U0074>";/
"<U0053><U0065><U0070><U0074><U0065><U006D><U0062><U0065><U0072>";/
"<U004F><U0063><U0074><U006F><U0062><U0065><U0072>";/
"<U004E><U006F><U0076><U0065><U006D><U0062><U0065><U0072>";/
"<U0044><U0065><U0063><U0065><U006D><U0062><U0065><U0072>"
% Appropriate date and time representation (%c)
% "%Y-%m-%d %H:%M:%S"
d_t_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
% Appropriate date representation (%x)
% "%Y-%m-%d"
d_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064>"
%
% Appropriate time representation (%X)
% "%H:%M:%S"
t_fmt "<U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
t_fmt_ampm ""
%
am_pm "";""
%
% Appropriate date representation (date(1)) "%Y-%m-%d %H:%M:%S"
date_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
END LC_TIME
LC_MESSAGES
copy "en_US"
END LC_MESSAGES
LC_PAPER
copy "en_US"
END LC_PAPER
LC_NAME
copy "en_US"
END LC_NAME
LC_ADDRESS
copy "en_US"
END LC_ADDRESS
LC_TELEPHONE
copy "en_US"
END LC_TELEPHONE
LC_MEASUREMENT
copy "en_US"
END LC_MEASUREMENT
linux date locale
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
I'd like to customize exclusively the date and time format for my system, while sticking to the rest of the locale as is. I know that environment variable LC_TIME will make it possible to customize that aspect only by pointing to an alternate locale. Since I am using Linux (Ubuntu 14.04 to be precise), I want to use the format understood by localedef as input.
I have read the following three pieces of documentation:
- http://pubs.opengroup.org/onlinepubs/009696699/basedefs/xbd_chap07.html
- http://manpages.ubuntu.com/manpages/trusty/man1/localedef.1posix.html
- https://ccollins.wordpress.com/2009/01/06/how-to-change-date-formats-on-ubuntu/
The last one was particularly helpful.
Now, I only want to customize the section for LC_TIME and would like to inherit verything else.
So I copied en_US to a file named isodate in /usr/share/i18n/locales and adjusted the values I care about. After sifting through the documentation I decided also to replace all other section contents with a copy-keyword.
Question: It's not clear to me what method is supposed to be best practice. Does anyone know that (or even another alternative than those given by me)?
For example, since I care only about a few values (d_t_fmt, d_fmt, t_fmt, t_fmt_ampm, am_pm, date_fmt) it would be sweet to inherit all of en_US for LC_TIME and then merely overwrite those values with my ISO-like format (ISO 8601). However, the documentation about copy states (emphasis mine):
copy
Specify the name of an existing locale which shall be used as the definition of this category. If this keyword is specified, no other keyword shall be specified.
This means I cannot simply throw in a copy and then add more keywords.
Also, might it be legit to only define the LC_TIME section or will localedef outright refuse to compile that?
TL;DR
What is the best practice for customizing my date and time format settings, while sticking to the DRY-principle, i.e. without repeating stuff unnecessarily?
What I came up with so far:
escape_char /
comment_char %
LC_IDENTIFICATION
copy "en_US"
END LC_IDENTIFICATION
LC_CTYPE
copy "en_US"
END LC_CTYPE
LC_COLLATE
copy "en_US"
END LC_COLLATE
LC_MONETARY
copy "en_US"
END LC_MONETARY
LC_NUMERIC
copy "en_US"
END LC_NUMERIC
LC_TIME
abday "<U0053><U0075><U006E>";"<U004D><U006F><U006E>";/
"<U0054><U0075><U0065>";"<U0057><U0065><U0064>";/
"<U0054><U0068><U0075>";"<U0046><U0072><U0069>";/
"<U0053><U0061><U0074>"
day "<U0053><U0075><U006E><U0064><U0061><U0079>";/
"<U004D><U006F><U006E><U0064><U0061><U0079>";/
"<U0054><U0075><U0065><U0073><U0064><U0061><U0079>";/
"<U0057><U0065><U0064><U006E><U0065><U0073><U0064><U0061><U0079>";/
"<U0054><U0068><U0075><U0072><U0073><U0064><U0061><U0079>";/
"<U0046><U0072><U0069><U0064><U0061><U0079>";/
"<U0053><U0061><U0074><U0075><U0072><U0064><U0061><U0079>"
week 7;19971130;7
first_weekday 1
first_workday 2
abmon "<U004A><U0061><U006E>";"<U0046><U0065><U0062>";/
"<U004D><U0061><U0072>";"<U0041><U0070><U0072>";/
"<U004D><U0061><U0079>";"<U004A><U0075><U006E>";/
"<U004A><U0075><U006C>";"<U0041><U0075><U0067>";/
"<U0053><U0065><U0070>";"<U004F><U0063><U0074>";/
"<U004E><U006F><U0076>";"<U0044><U0065><U0063>"
mon "<U004A><U0061><U006E><U0075><U0061><U0072><U0079>";/
"<U0046><U0065><U0062><U0072><U0075><U0061><U0072><U0079>";/
"<U004D><U0061><U0072><U0063><U0068>";/
"<U0041><U0070><U0072><U0069><U006C>";/
"<U004D><U0061><U0079>";/
"<U004A><U0075><U006E><U0065>";/
"<U004A><U0075><U006C><U0079>";/
"<U0041><U0075><U0067><U0075><U0073><U0074>";/
"<U0053><U0065><U0070><U0074><U0065><U006D><U0062><U0065><U0072>";/
"<U004F><U0063><U0074><U006F><U0062><U0065><U0072>";/
"<U004E><U006F><U0076><U0065><U006D><U0062><U0065><U0072>";/
"<U0044><U0065><U0063><U0065><U006D><U0062><U0065><U0072>"
% Appropriate date and time representation (%c)
% "%Y-%m-%d %H:%M:%S"
d_t_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
% Appropriate date representation (%x)
% "%Y-%m-%d"
d_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064>"
%
% Appropriate time representation (%X)
% "%H:%M:%S"
t_fmt "<U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
%
t_fmt_ampm ""
%
am_pm "";""
%
% Appropriate date representation (date(1)) "%Y-%m-%d %H:%M:%S"
date_fmt "<U0025><U0059><U002D><U0025><U006D><U002D><U0025><U0064><U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053>"
END LC_TIME
LC_MESSAGES
copy "en_US"
END LC_MESSAGES
LC_PAPER
copy "en_US"
END LC_PAPER
LC_NAME
copy "en_US"
END LC_NAME
LC_ADDRESS
copy "en_US"
END LC_ADDRESS
LC_TELEPHONE
copy "en_US"
END LC_TELEPHONE
LC_MEASUREMENT
copy "en_US"
END LC_MEASUREMENT
linux date locale
linux date locale
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
edited Aug 21 '18 at 20:12
0xC0000022L
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
asked May 17 '15 at 22:49
0xC0000022L0xC0000022L
8,02415 gold badges70 silver badges131 bronze badges
8,02415 gold badges70 silver badges131 bronze badges
3
It's ok to only define one section and copy the other ones...
– don_crissti
May 17 '15 at 23:23
2
@K7AAY - that tag is completely irrelevant. There is absolutely nothing Ubuntu-specific here.
– don_crissti
Aug 21 '18 at 18:38
You might want to take a look at en_DK.UTF-8 :) I guess it's what you want.
– Pierre-Alain TORET
Oct 17 '18 at 10:07
add a comment |
3
It's ok to only define one section and copy the other ones...
– don_crissti
May 17 '15 at 23:23
2
@K7AAY - that tag is completely irrelevant. There is absolutely nothing Ubuntu-specific here.
– don_crissti
Aug 21 '18 at 18:38
You might want to take a look at en_DK.UTF-8 :) I guess it's what you want.
– Pierre-Alain TORET
Oct 17 '18 at 10:07
3
3
It's ok to only define one section and copy the other ones...
– don_crissti
May 17 '15 at 23:23
It's ok to only define one section and copy the other ones...
– don_crissti
May 17 '15 at 23:23
2
2
@K7AAY - that tag is completely irrelevant. There is absolutely nothing Ubuntu-specific here.
– don_crissti
Aug 21 '18 at 18:38
@K7AAY - that tag is completely irrelevant. There is absolutely nothing Ubuntu-specific here.
– don_crissti
Aug 21 '18 at 18:38
You might want to take a look at en_DK.UTF-8 :) I guess it's what you want.
– Pierre-Alain TORET
Oct 17 '18 at 10:07
You might want to take a look at en_DK.UTF-8 :) I guess it's what you want.
– Pierre-Alain TORET
Oct 17 '18 at 10:07
add a comment |
1 Answer
1
active
oldest
votes
I created a very similar locale recently and as Pierre-Alain suggested I used en_DK.UTF-8 as my template. I don't think that there are any strict best practices as can be seen by looking at the differences between the standard locales that are shipped with most Linux distributions.
You can read about how I solved my problem on my web site and look at the final result on gitlab.
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f203975%2fbest-practice-to-customize-date-time-format-system-wide%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I created a very similar locale recently and as Pierre-Alain suggested I used en_DK.UTF-8 as my template. I don't think that there are any strict best practices as can be seen by looking at the differences between the standard locales that are shipped with most Linux distributions.
You can read about how I solved my problem on my web site and look at the final result on gitlab.
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
add a comment |
I created a very similar locale recently and as Pierre-Alain suggested I used en_DK.UTF-8 as my template. I don't think that there are any strict best practices as can be seen by looking at the differences between the standard locales that are shipped with most Linux distributions.
You can read about how I solved my problem on my web site and look at the final result on gitlab.
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
add a comment |
I created a very similar locale recently and as Pierre-Alain suggested I used en_DK.UTF-8 as my template. I don't think that there are any strict best practices as can be seen by looking at the differences between the standard locales that are shipped with most Linux distributions.
You can read about how I solved my problem on my web site and look at the final result on gitlab.
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
I created a very similar locale recently and as Pierre-Alain suggested I used en_DK.UTF-8 as my template. I don't think that there are any strict best practices as can be seen by looking at the differences between the standard locales that are shipped with most Linux distributions.
You can read about how I solved my problem on my web site and look at the final result on gitlab.
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
answered Oct 23 '18 at 12:07
gam3gam3
1961 silver badge9 bronze badges
1961 silver badge9 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f203975%2fbest-practice-to-customize-date-time-format-system-wide%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
It's ok to only define one section and copy the other ones...
– don_crissti
May 17 '15 at 23:23
2
@K7AAY - that tag is completely irrelevant. There is absolutely nothing Ubuntu-specific here.
– don_crissti
Aug 21 '18 at 18:38
You might want to take a look at en_DK.UTF-8 :) I guess it's what you want.
– Pierre-Alain TORET
Oct 17 '18 at 10:07