Bug 101304 - CALC, Time entry, 16:10:29 displays as 16🕙29; :10:, :11:, :12: are problems, Other minutes values o.k.
Summary: CALC, Time entry, 16:10:29 displays as 16🕙29; :10:, :11:, :12: are problems, ...
Status: RESOLVED DUPLICATE of bug 97191
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-04 17:06 UTC by Tom
Modified: 2016-08-04 17:39 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom 2016-08-04 17:06:22 UTC
User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Build Identifier: LibreOffice 5.1.4.2 Version: 5.1.4.2 Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a CPU Threads: 8; OS Version: Windows 6.1; UI Render: GL;  Locale: en-US (en_US)

I have been entering a series of times in a column. (The time format is HH:MM:SS AM/PM; 01:37:46 PM). I have entered the times in 24 hour format, since I am entering them in from another source. I am typing the times in by hand, not doing a copy and paste. Calc has been changing them correctly to AM/PM format, except where 10, 11, or 12 is the number of minutes.  It displays an open square for the ":10:", ":11:", ":12:";  i.e. 16🕙29 as soon as I type in the second colon.

I have to put a different number in for the 10, then after entering the complete time, Hours, minutes and seconds and pressing enter, I go back in and change the number to 10 for it to display correctly.

This is the same thing that occurs if I enter a single digit in for the minutes, instead of 01, 02, 03, ..., 09. That is easily fixed by typing in the zero in front of the single digit. A 0 for 00 minutes works O.K.

A single digit can be entered in for hours or seconds, but not minutes, except for 0 minutes. 

The error happens whether I type the time directly into the cell, or into the input line at the top of the sheet.

Enter time directly
03:54:38 PM
09:53:39 AM
04:04:20 PM
04:06:51 PM
16🕙29
16🕛16

Work around entry. Putting incorrect minutes in for 10 - 12.
03:54:38 PM
09:53:39 AM
04:04:20 PM
04:06:51 PM
04:13:29 PM
04:13:16 PM


Updated entry after editing the minutes
03:54:38 PM
09:53:39 AM
04:04:20 PM
04:06:51 PM
04:10:29 PM
04:12:16 PM

As I was typing in these details, I found another workaround. Just like the entry for single digits, put a zero in front of the number.

Workaround number 2, add an additional zero in front of the 10, 11 or 12 minutes.

On a side note, but possibly related, I thought at one time that I could enter in a single digit for the minutes, but maybe that was just the zero minutes.

Reproducible: Always

Steps to Reproduce:
1.Format column cells with HH:MM:SS AM/PM; 01:37:46 PM from either CTRL-1 or format menu.
2.Enter time in the cell
3.When the : after the 1 - 12 minutes entry is typed in, the minutes becomes an open square
Actual Results:  
The error happens whether I type the time directly into the cell, or into the input line at the top of the sheet.

Enter time directly
03:54:38 PM
09:53:39 AM
04:04:20 PM
04:06:51 PM
16🕙29
16🕛16

Expected Results:  
03:54:38 PM
09:53:39 AM
04:04:20 PM
04:06:51 PM
04:10:29 PM
04:12:16 PM

If a number other than 10, 11, 12 is typed in for the minutes, i.e. 0, 00, 01, 02, 03, ..., 09 or 13 and above, enter is pressed, then edited to the correct number 10, 11, or 12 or if a leading zero is typed in before numbers 1 - 12, the minutes comes out correctly


[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes

Windows 7 Ultimate Service Pack 1
System Rating: 5.2 Windows Experience Index
Processor: Intel Core i7 920 @ 2.67 GHz
Installed Ram: 24.0 GB
System Type: 64- bit operating system
Pen and Touch: No Pen or Touch Input


Reset User Profile?No
Comment 1 Aron Budea 2016-08-04 17:39:05 UTC
Please refer to bug 97191.

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