Description: I checked Korean Line break rules file ( i18npool/source/localedata/data/ko_KR.xml ). So, I also checked Korean LC_FORMAT, DateAcceptancePattern rule. In Korean Date notations, 'M/D' doesn't use in Korean. As a Korea Standard(Republic of Korea's agency Korean Standards Association - KS X ISO8601), Date notation follows ISO 8601 — Date and time format. So, The Korean Version of MS Excel displays dates based on ISO8601. Also, As a Hangul orthography(한글맞춤법), the overall rules of writing the Korean language with Hangul, Date notation uses '.' Use of ' - (2) Arabic numerals alone to indicate the date of the year, month and day. Example) 1919. 3. 1. 2008년 5월 → 2008. 5. 7월 22일 → 7. 22. As a result, In Korean, both "YYYY-MM-DD"(ISO8601) and "YYYY. MM. DD."Hangul orthography(한글맞춤법)" are public and usually use in Korean. Steps to Reproduce: 1. Tools -> Options -> Language Settings -> Languages 2. 3. Actual Results: Date Acceptance patterns: Y/M/D;M/D; Expected Results: Date Acceptance patterns: Y/M/D;M/D; Reproducible: Always User Profile Reset: No Additional Info: Date Acceptance patterns: Y-M-D;M-D;M.D.;M월D일;Y.M.D.;Y년M월D일
The example of Unicode CLDR - Korean Date/Time charts. https://unicode-org.github.io/cldr-staging/charts/latest/verify/dates/ko.html
DaeHyun Sung committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9a873383868814e18de8d205a03c0824c74b6d56 tdf#143295 fix DateAcceptancePattern in Korean It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
DaeHyun Sung committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/0f999f33dcaf1e830ddf8d45aa36b8ef1b2a9ff3 tdf#143295 fix DateAcceptancePattern in Korean It will be available in 7.2.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
If Y/M/D and M/D aren't used, shouldn't then all YYYY/MM/DD and MM/DD format codes be changed to YYYY-MM-DD and MM-DD and the date separator be '-' instead of '/'? And if "YYYY. MM. DD." is a standard format, shouldn't then also "Y. M. D." (with blanks) and "M. D." be in the date acceptance patterns?
Dear DaeHyun Sung, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assign it back to yourself if you're still working on this.
Dear DaeHyun Sung, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug