AFAIK (Bug 30714, Bug 30715) its planned (or already done?) to have a shortcut to insert current date or current date into a cell. We already have something listed in menu "Tools -> Customize": <Cntrl> = 'Options -> Insert Current Date' <Cntrl>+<Shift> = 'Options -> Insert Current Date' It seems there is a problem to have shortcuts with punctuation marks in the list? Currently these items are missing in WIKIHELP.
In the other Writer like applications from other vendors, exists lot of shortcuts to help on EDITING making you more productive. A firts lists of them is: Shift+F3 Change Uppercase/Lowercase (press once per option) Ctrl+< Decrease 1 point character size Ctrl+> Increase 1 point character size Ctrl+= Set character to be subindex Ctrl++ Set character to be superindex Ctrl+SPACE BAR Set character to Default format Ctrl+Shift+1 Set style Header 1 Ctrl+Shift+2 Set style Header 2 Ctrl+Shift+3 Set style Header 3 Ctrl+Shift+4 Set style Header 4
Is very important for accessibility reasons, to add at the menu the shortcut to call each item it has. If one is missing please add it. If the menu item opens a dialog, add a shurtcut to it and show to the user the combination of keys he/she need to press in order to call it.
Some comments on the keyboard shortcuts described by esodan: The following shortcuts are already in LibreOffice Writer: Ctrl+M Set default formatting (for current style) Ctrl+0 Set style Text Body Ctrl+1 Set style Header 1 Ctrl+2 Set style Header 2 Ctrl+3 Set style Header 3 Ctrl+4 Set style Header 4 Ctrl+5 Set style Header 5 (www.odfauthors.org - previously www.oooauthors.org - has/has a document with keyboard shortcuts, as an appendix to the Writer Guide.) However, Rainer Bielefeld's comment is about Calc, not about Writer.
I checked with Master "LibO-dev 3.4.5 – WIN7 Home Premium (64bit) English UI [(Build ID:d337f79-a24c961-2865670-9752b71-7f8fd43 2fdd60d-fd28b6a-fd7bf20-aa369cb-28da3fb 6a9633a-931d089-ecd263f-c9b55e9-b31b807 82ff335-599f7e9-bc6a545-1926fdf)]" Shortcut Insert Date Customize shows that it should be ctrl+shift+; That does nothing with a german key board Keyboard layout problem?
My mistake, of course Shortcut "Insert current TIME" is 'ctrl+shift+;' I doubt that such a keyboard layout dependent relation can be used without problems?! Currently I don't have a complete overview concerning all related problems, but there can't be any doubt, we have a problem here, so CONFIRMED. @David At least 'ctrl+shift+;' is missing in Help, also some others from Comment 1 are missing @Christoph: You know, here is my question concerning general considerations? @sophie: Who can check localization issues? @Kohei: Please feel free to reassign if it’s not your area or if provided information is not sufficient.
not only the shortcut <Control> + ; are affected, there are also the Shortcuts <Control> + [ and <Control> + ]
(In reply to comment #5) > @Christoph: > You know, here is my question concerning general considerations? Sorry, I lack knowledge on (existing) general considerations in this case. In the past, decisions on new keyboard shortcuts have often be made with regard to competitor products (if not interfering with existing shortcuts). Usually, it is hard to apply any _serious_ scheme (but e.g. the difference Ctrl+ or Ctrl+Shift+). What may help here for time/date functions in comparison to the large competitor product (2007) - they also have different shortcuts in German vs. English. So it seems such items are localized. * German: STRG+UMSCHALT+; Aktuelle Zeit einfügen * English: CTRL+SHIFT+: Enters the current time.
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
** 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.0.4 or later) 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** 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
*** This bug has been marked as a duplicate of bug 88027 ***