Impress, Draw, Calc, and Writer uses Ctrl+U for Underline (single). 

In Writer ctrl+D is defined as Underline:Double.
Calc uses this shortcut for Fill Down (Underline:Double is empty).
Impress/Draw do not provide direct access to double underline (you can apply it via character > font effects > underlining) and haven't defined the shortcut ctrl+D.

The actual question is if a shortcut to double underline in Impress/Draw is really required. And even in Calc it's questionable since you better format the final text in Writer. Plus, ctrl+D is not the best shortcut for this function. So if we go with double underline everywhere it should be shift+ctrl+U (free in all modules).

If we want to have a shortcut for double underline, then it would be ideal to have it consistent across the apps, so if shift+ctrl+U is free in all modules, then that seems like a good choice to use.

Just as a note, i havent found any word processor that has a shortcut for double underline.

<in_geenral>
I can imagine that a hotkey like Ctrl+<whatever> is more needed for a function #1 in one application while the same hotkey is more beneficial for function #2 in another application. 

Different applications have different purposes and the simple fact that both of app#1 and app#2 are capable to do something, it doesn't mean that those functionalities are identically important in those applications and it means even less that the same hotkey should be used.

Thus, I don't think we should obey the same hotkey => same functionality rule.
</in_geenral>

<in_concrete_case>
The question here is that is the double underline functionality such a widely used one that it should have the same hot key or it is not. 

In my experience, it is a very rarely used formatting so I don't think I will ever need it. If somebody does then they still can change the keyboard in Tool => Customize => Keyboard.
</in_concrete_case>

We discussed the idea in the design meeting and think consistency is paramount. Therefore double underline should be available in all modules, however with a consistent shortcut where shift+ctrl+U is a good option.

Patch has been submitted but for some reason it doesn't work. Question is if shift+ctrl+U should still be used since Gnome takes this shortcut for the unicode input.

For the record, Ctrl+D is the shortcut for "document properties" in some programs, e.g. PDF-XChange and Acrobat.

Shift+ctrl+U cannot work since it interferes with ctrl+U, see bug 114010 (containing link to the preliminary patch).

Bug still present in 6.1.5.1



How about short-cut key "Ctrl+Shift+D"

(In reply to Tad Whiteside from comment #11)
> How about short-cut key "Ctrl+Shift+D"

Don't like it as you have to remember another key. But ctrl/cmd+alt+U could work.

(In reply to Heiko Tietze from comment #12)
> (In reply to Tad Whiteside from comment #11)
> > How about short-cut key "Ctrl+Shift+D"
> 
> Don't like it as you have to remember another key. But ctrl/cmd+alt+U could
> work.

Ctrl+Alt+U would create another problem like those in bug #107244 for certain keyboard localizations...
For example in Hungarian on Windows that creates this character: €

Version: 7.0.1.2

Bug still present (ie inconsistent way of getting double underline across libreoffice applications)

I originally reported this because I use Calc to generate accounting reports. I'm US-based, so the double underline is a common format in accounting documents.

Multi-language/culture/operating system - It's a tricky problem.

Perhaps the alt+<hypen-underline key> for double underline (since shift+<hypen-underline key> is underline).

Thanks for the hard work.

Dear Tad Whiteside,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug