Created attachment 120880 [details] sample demo sheet Testing the function ORARIO.VALORE (TIMEVALUE in EN) I have found that any combination of topics gives as result Err:502. See a demo in the attached sheet "orario funct.ods" (the same two examples into the help).
Hi @gmarco, thanks for reporting. Sorry but for me cells from B11 to F12 shows properly the values, no Err:502 (Invalid argument) results for me.
I get Err:502 for B11, D11 and F11. Win 7 Pro 64-bit, Version: 5.0.3.2 (x64) Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: fi-FI (fi_FI) Version: 5.2.0.0.alpha0+ Build ID: a7c3a2a9be83686657c06f37d521f9f6d2004ddd Threads 4; Ver: Windows 6.1; Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2015-11-28_04:39:18 Locale: fi-FI (fi_FI) LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Note: I could make it work in a new document, if I used the style of my own locale: "4ip." instead of "4PM". Yet, the Italian help speaks of "4PM", so it should work: https://help.libreoffice.org/Calc/TIMEVALUE/it gmarco: please try to find out, if Italian help is correct..
OK with French locale. Err 502 with Italian one. But when I check time format for Italian locale, I see 4p. or 4s. instead of 4PM and 4AM. Formula =ORARIO.VALORE("4P.") returns correct value. I don't know if the error is in the settings or in the help (I don't know Italian use for times format)
Created attachment 120903 [details] newtest screenshot Thanks to everyone, primarily to Beluga. In the attachment you can see my test: "PM" has to be "P." or "M.", the letter can be upper or lower case, a space is also ok between the hour number and the letter. So the italian help seems wrong, but I don't know which is the official and right italian time format, I am used to see on the digital clocks the symbols am and pm (lower or upper case), never I have seen m. or p.
(In reply to gmarco from comment #5) > Created attachment 120903 [details] > newtest screenshot > > Thanks to everyone, primarily to Beluga. > In the attachment you can see my test: "PM" has to be "P." or "M.", the > letter can be upper or lower case, a space is also ok between the hour > number and the letter. > So the italian help seems wrong, but I don't know which is the official and > right italian time format, I am used to see on the digital clocks the > symbols am and pm (lower or upper case), never I have seen m. or p. I guess you should discuss in one of the Italian mailing lists. I'll change component to documentation and adjust summary.
(In reply to Beluga from comment #6) > > I'll change component to documentation and adjust summary. OK, thanks > I guess you should discuss in one of the Italian mailing lists. If you consider that the Italian forum (ask.libreoffice.org/it/questions/) has a total of 68 questions only, you can realize what result could have a similar survey.
(In reply to gmarco from comment #7) > (In reply to Beluga from comment #6) > > > > I'll change component to documentation and adjust summary. > > OK, thanks > > > I guess you should discuss in one of the Italian mailing lists. > > If you consider that the Italian forum (ask.libreoffice.org/it/questions/) > has a total of 68 questions only, you can realize what result could have a > similar survey. I meant the mailing lists: http://nabble.documentfoundation.org/Italian-f1816772.html https://wiki.documentfoundation.org/Local_Mailing_Lists#Italian The Italian community is huge..
(In reply to Beluga from comment #8) > I meant the mailing lists: > http://nabble.documentfoundation.org/Italian-f1816772.html > https://wiki.documentfoundation.org/Local_Mailing_Lists#Italian > > The Italian community is huge.. Thanks, you are right, unfortunately I am quite busy on other fronts, asap I'll try to get into those forums.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
(In reply to QA Administrators from comment #10) Running LO 5.2.3.3 Win10 nothing changed. Look at the new attachment for some examples and notes. Further I note that anti and post meridian espress in Calc with the letters "m" and "p" are unusual in IT: I translate what you can read about at the link http://tp.linux.it/data_ora_valuta.html TIMEVALUE. The conventional notation to indicate a time in Italian language is "o:mm:ss" with the hour expressed in 24-hour format without leading zero. Expressed in the syntax of the GNU program date(1) becomes: %k:%M:%S Examples: 13:00:56 4:12 The presence of leading zeros (obtained with dates(1) by replacing the %k with %H) is allowed in case you have the need for alignment issues or ordering. It should be noted, that only for the alignment motivation, the agreement for date(1) provides for the possibility to use the "_" and "-" modifiers to hide some digit. Consult the man page for more information. In case you must use the 12-hour format, morning and afternoon should be rendered as "a.m." and "p.m.". Any other expression (AM/PM or A.M./P.M and so on) is to be avoided. Also in case you must use the 12-hour format, the issue date(1) to use for the hour is %-I
Created attachment 130160 [details] ods sample
I notice that the summary title has been changed, but do not agree with the new text ("TIMEVALUE Calc function described incorrectly in the Italian documentation"): the description is not incorrect and it is not so only in the Italian Doc, the substance is a very poor documentation about the offered examples and the only two present get "Err: 502". As I show in the sample ods already attached, the right format for the arguments are not exemplified [es. = TIMEVALUE ("4P.") O = TIMEVALUE ("16:00")]. Also for the example in the help function "=ORARIO" (in IT) is wrong: it says "= ORARIO (4;20;4) restituisce 04:20:04" ("restituisce" = displays) but it is not so, it displays "4.20.04"(. instead of :). Also there are problems with the documentation but also problems regarding the results: - the m. and p. suffixes are unusual in IT (we usually use a.m. and p.m. or simply am and pm) - results as "=ORARIO(0;0;0) = 12.00.00m." or "=ORARIO(24;35;15) = 12.35.15m." are unacceptable. Therefore, if you prefer, I can split the question in two separate bugs, let me know.
if there are 2 separate issues is always better to spit the report into 2 different ones. once you have done it, set the current status here to RESOLVED MOVED and put links to the new bug reports under the "See Also" field (top right of the page.
As required, being the question a mixture of incorrect documentation and probable bugs affecting two different functions in Calc, I divided this one in 4 distinct bugs: 105221, 105222, 105224, 105226