Description: Inserting the current date using a shortcut key does not take into account the number of years, you can only insert a simple date. There is no option to change this, it is a completely meaningless function. The purpose of inserting the current date is to keep track of the present, that is, the year, month, and day. This creates confusion when the years go by. this year's date? next year? or last year? The current time insertion needs to be changed to insert all dates. As fast as possible. I don't want to use libre6.3.4. Not suitable for normal use at all due to the crash and instability in kdeneon5.17. Steps to Reproduce: 1.Set Customize> Insert Current Date to the applicable key. Actual Results: 2.Insert current date Expected Results: You will see that only the date is inserted Reproducible: Always User Profile Reset: Yes Additional Info: Current date should include years
6.2.8 is last official LO version (see https://wiki.documentfoundation.org/ReleasePlan/6.2). So if there's a bug about this on 6.2.8 and you don't want to use 6.3.4 because of regressions, you're stuck. Now about 6.3.4, you can report crashes so they could be fixed or you can try other rendering than kf5 (= kde5). For example: - launch term/console - export SAL_USE_VCLPLUGIN=gen - soffice
Created attachment 156778 [details] Text function "0" sets referrer number to 0
We could reproduce the bug. Take a look at sheet 2 with the attached file. The number that should be 23 will be 0 by the text function This happens when the referrer uses concat or sum. Some combinations do not occur, but it is unclear why they do. Of course I updated to 6.2.3.8 and deleted the configuration file before checking. Older versions would be wrong to report bugs. But even the latest version had bugs. What do you think? Does this not happen in beta version etc?
oh, i mistake. sorry. I filed another bug file. And updated to 6.3.4.2. The date is sure to insert 2019/12/26, but the display in libre is ###. How to fix this?
I want to know how to display the date without expanding the cell width. And when the date is inserted in the Japanese language, it is written as "XX month XX day" "12月26日" in the cell. "Dec 26" in English (US) language. There is no year in any language notation. i want view this. If it is a Japanese language, it will be December 26, 2019. "2019年12月26日" It is 2019/12/26 in English. What are the settings for displaying the "year month day" in this date-inserted cell?
(In reply to gyrlgith from comment #5) > I want to know how to display the date without expanding the cell width. > And when the date is inserted in the Japanese language, it is written as "XX > month XX day" "12月26日" in the cell. > "Dec 26" in English (US) language. > There is no year in any language notation. > > i want view this. > If it is a Japanese language, it will be December 26, 2019. "2019年12月26日" > It is 2019/12/26 in English. > > What are the settings for displaying the "year month day" in this > date-inserted cell? On Pc Debian x86-64 with LO master sources updated today or with LO Debian package 6.3.4, if I do Ctrl+; I got: 27/12/19 (27th december of 2019). So I think it depends on locale parameter (Options/Tools/Languages).
(In reply to Julien Nabet from comment #6) > On Pc Debian x86-64 with LO master sources updated today or with LO Debian > package 6.3.4, if I do Ctrl+; > I got: 27/12/19 (27th december of 2019). > So I think it depends on locale parameter (Options/Tools/Languages). thank you, i set locale English(USA). ok input 01/07/2020, but one problem. this see default width cell = ### input hand write > 2020-01-07 how view data not ###?
japanese locale is only "1月7日" dosen't change view. why?
(In reply to gyrlgith from comment #8) > japanese locale is only "1月7日" > dosen't change view. why? Isn't just width of the column? I mean if you increase width of the column it should be ok.
(In reply to Julien Nabet from comment #9) > (In reply to gyrlgith from comment #8) > > japanese locale is only "1月7日" > > dosen't change view. why? > > Isn't just width of the column? I mean if you increase width of the column > it should be ok. Hello gyrlgith, is the issue fixed if you increase the column's width ?
Created attachment 158047 [details] only month and day
(In reply to Julien Nabet from comment #9) > Isn't just width of the column? I mean if you increase width of the column > it should be ok. (In reply to Xisco Faulí from comment #10) > Hello gyrlgith, > is the issue fixed if you increase the column's width ? hi sorry late info. thanks help. i created screenshot on ods. test use method. for data input on hand write, and on hotkey. change locale to Japanese set. hardwrite. = hotkey. with locale defaults. i use this everyday. i no use locale Japanese. write with hotkey. = hotkey on locale Japanese. japanese locale and English locale with using increase cell width. i want to view data is %Month%Day%Year on default cell width. example 20/02/21. so not ###. how? yes, i no using japanese locale. is not in trouble to data view for %月%日. but this default cell width auto view data ### is useless on many locale.
[Automated Action] NeedInfo-To-Unconfirmed
In Japanese locale, the default date formatting is "M月D日" I'm not sure this is by design or not, but it's incompatible with Excel (always "yyyy/m/d")
(In reply to Naruhiko Ogasawara from comment #14) > In Japanese locale, the default date formatting is "M月D日" > I'm not sure this is by design or not, but it's incompatible with Excel > (always "yyyy/m/d") This link may help: https://ask.libreoffice.org/en/question/158048/how-do-i-change-the-default-datetime-format/
The ja-JP locale data has M月D日 as the default medium date display format, apparently on purpose as users expect it (or at least did so 15 years ago), this is also used as the default date format when a date is entered in a cell not using the shortcut. All number formatting depends on the locale, either system locale, LibreOffice locale or the cell's locale depending on what was individually assigned where. Also for inserting a date with the shortcut the current cell formatting is taken into account. If no cell format was assigned then the LibreOffice default locale's default date format is used. If the result happens to be ### it just means the column is too narrow to display that (numeric) formatted result, so widen the column by hitting Shift+Alt+Right on that cell to make it fit (or use a smaller font size). Now, so far there is no bug. Or is this a request to change the default Japanese medium date format? Are there any references what the correct date format would be? So far there are no complaints as far as I know, so I take it that the majority of Japanese users are happy with the choice. "Excel uses yyyy/m/d" is not a compelling view to that regard, but maybe it should be YYYY年M月D日 instead? Just how widespread is that used and expected as a default date display format in spreadsheets?
(In reply to Eike Rathke from comment #16) > Or is this a request to change the default Japanese medium date format? Are > there any references what the correct date format would be? So far there are > no complaints as far as I know, so I take it that the majority of Japanese > users are happy with the choice. "Excel uses yyyy/m/d" is not a compelling > view to that regard, but maybe it should be YYYY年M月D日 instead? Just how > widespread is that used and expected as a default date display format in > spreadsheets? hi. im said no need fix view data for M月D日 reply before. because im no use Japanese launguage everyday. simple. im want view cell style to ### > MM/DD/YY Libraoffice calc. if cell empty neighbor = you can view input data is no omission data. example AAAAAAAAAAAAAAAA|empty cell| > AAAAAAAAAAAAAAAA.. that is no omission, no ###. right? but why omission is only data?
i tried both version Version: 7.0.4.2 Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 8; OS: Mac OS X 10.13.6; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded and Version: 7.2.0.0.alpha0+ Build ID: 90668f3473f4e52cec823ad39c6fcb44ba7c089b CPU threads: 8; OS: Mac OS X 10.13.6; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded it shows 01/11/21 on the screen. it works for me . Not reproduce bug.
Please make a summary what is the point of this bug, with exact steps to reproduce.
Dear gyrlgith, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear gyrlgith, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp