Bug 90571 - Writer: UI: searching in Special Characters by various ways; scrolling; and dialog's/command's name
Summary: Writer: UI: searching in Special Characters by various ways; scrolling; and d...
Status: RESOLVED DUPLICATE of bug 34882
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.8.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-11 21:29 UTC by Nick Levinson
Modified: 2016-09-15 15:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screencast when font menu active (438.14 KB, video/webm)
2015-04-18 20:04 UTC, Nick Levinson
Details
screencast when subset menu active (798.11 KB, video/webm)
2015-04-18 20:12 UTC, Nick Levinson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Levinson 2015-04-11 21:29:55 UTC
The Special Characters dialog needs to be better at supporting a search.

I'd like to search by character name, Unicode identifier, hex position, and decimal position. It's easier to get an em-dash by going to Wikipedia's article about the dash and copying the character for pasting. I found U+2012 through U+2015 in the DejaVu Serif font General Punctuation subset, but I don't know which one is the em-dash.

The vertical scroll bar is confusing. I expect more characters in the font's subset, but dragging the scroll bar down counterintuitively takes me to another font if the font menu is preselected or to another subset if the subset menu is preselected.

Although the menu item is appropriately named, the dialog is misnamed; clearly it includes nonspecial characters, like 0–9, A–Z, and a–z, as well as special ones. I'd just name it Characters.

I'm running LibreOffice 4.2.8.2, which is still being updated even if it is at EOL. If these features have been added to the latest LibreOffice version, that's good enough.

I guessed my hardware.
Comment 1 Yousuf Philips (jay) (retired) 2015-04-11 21:52:44 UTC
Hello Nick,

We have plans to improve on the special characters dialog, which can be seen here.

http://user-prompt.com/libreoffice-design-session-special-character/

I'm assuming it covers all the suggestions you've made.
Comment 2 Nick Levinson 2015-04-12 22:04:56 UTC
Yes, except the scroll issue, which I've since brought there, by adding into the existing topic. Thanks.
Comment 3 Yousuf Philips (jay) (retired) 2015-04-13 08:38:35 UTC
The scroll issue is not reproducible for me. What operating system are you running on? Is it possible to send in a screencast so we can see this behaviour in action.
Comment 4 Buovjaga 2015-04-17 17:15:53 UTC
Set to NEEDINFO while we wait for further information.
Comment 5 Nick Levinson 2015-04-18 20:04:37 UTC
Created attachment 114893 [details]
screencast when font menu active
Comment 6 Nick Levinson 2015-04-18 20:12:37 UTC
Created attachment 114895 [details]
screencast when subset menu active
Comment 7 Nick Levinson 2015-04-18 20:17:21 UTC
Partly still the case; partly my error. I figured out what's happening. My laptop's touchpad supports scrolling by my dragging two spread-apart fingers down the touchpad, and scrollbars usually deal with that as if I had mouse-dragged the scroll bar down. So I got used to doing that and thinking of it as mousing (my laptop has no mouse). However, the Special Characters dialog deals with the two dragging methods differently. The two-finger touchpadding got the effect I described that you couldn't replicate, and I uploaded screencasts of it.
Comment 8 Yousuf Philips (jay) (retired) 2015-04-19 11:36:01 UTC
Hi Nick,

Thanks for the screencasts. I checked the same with my laptop touchpad and could only reproduce your behaviour when the mouse is outside of the boundaries of character list control and the font drop down is selected, which it is when you first open the dialog.

I believe the solution to this is that the character list control should be the one with focus when the dialog opens up. This is the behaviour other word processors.
Comment 9 Volga 2015-11-11 07:02:29 UTC
I think the Special Characters dialog should including a input box to let user searching character by exact name or codepoint.
Comment 10 Volga 2015-11-12 06:50:28 UTC
(In reply to General Kutuzov from comment #9)
> I think the Special Characters dialog should including a input box to let
> user searching character by exact name or codepoint.

BabelMap[1] and BabelPad[2] have implemented this method.

[1] http://babelstone.co.uk/Software/BabelMap.html
[2] http://babelstone.co.uk/Software/BabelPad.html
Comment 11 Yousuf Philips (jay) (retired) 2015-11-17 13:06:43 UTC
(In reply to General Kutuzov from comment #9)
> I think the Special Characters dialog should including a input box to let
> user searching character by exact name or codepoint.

Yes searching by a character's name is part of the extended proposal. If codepoint is the character's unicode number, that will be implemented in the basic proposal.

(In reply to General Kutuzov from comment #10)
> BabelMap[1] and BabelPad[2] have implemented this method.
> 
> [1] http://babelstone.co.uk/Software/BabelMap.html
> [2] http://babelstone.co.uk/Software/BabelPad.html

I dont think LO needs to fully compete with Character Map apps.
Comment 12 Volga 2016-02-20 20:38:10 UTC
(In reply to General Kutuzov from comment #9)
> I think the Special Characters dialog should including a input box to let
> user searching character by exact name or codepoint.

(In reply to General Kutuzov from comment #10)
> (In reply to General Kutuzov from comment #9)
> > I think the Special Characters dialog should including a input box to let
> > user searching character by exact name or codepoint.
> 
> BabelMap[1] and BabelPad[2] have implemented this method.
> 
> [1] http://babelstone.co.uk/Software/BabelMap.html
> [2] http://babelstone.co.uk/Software/BabelPad.html

OK, the current version of LibreOffice can do it.
Comment 13 Yousuf Philips (jay) (retired) 2016-02-21 02:26:37 UTC
Yes the 5.1 release now adds ascii and hexadecimal searching in the dialog. I'm closing this as a duplicate of the main bug that is pursuing the fixes mentioned in the blog post.

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