https://bugs.documentfoundation.org/show_bug.cgi?id=91758
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needsDevEval
CC| |erack@redhat.com
Component|UI |Calc
--- Comment #8 from Heiko Tietze <tietze.heiko@gmail.com> ---
(In reply to Wolfgang Jäger from comment #7)
Will there be an opportunity to discuss the topic somewhere without writing
reports, messages, comments, whatever most likely to no effect at all. It's
all too narrow, and often misunderstandings cannot be expelled.
You are very welcome to the design meetings, at the IRC channel, and on
Telegram.
https://wiki.documentfoundation.org/Design
But your report is clear to me (as native German who prefers English UI it's
always 'surprising' how numbers are converted). On the other hand, Stuarts
reply is also reasonable. And we will not change how numbers are converted. And
actually there are plenty of functions to deal with datetime.
What I could imagine is better feedback. When you insert 5-1-15 and press Enter
the text could fade into a grey M-D-Y (depending on how it works) that fades
into the final Jun/01/20015 (or whatever). Eike, what do you think?
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 91758] dash delimited dates entered are not correctly interpreted as Y-M-D in specific cases · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.