Newline (¶) only selectable after punctuation or space

Bug #579181 reported by Paul Sladen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Dasher
New
Medium
dasher (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: dasher

Entering constructs such as:

  /win 123[enter]

(for Irssi) via Dasher is impossible as Dasher only allows hitting the [ ¶ ] square after punction (!/./,/...) or a space (' '). Ideally Dasher should allow entering an enter at any time. This may just be a case of it not being in the training database.

Paul Sladen (sladen)
Changed in dasher (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Alan Bell (alanbell) wrote :

I have been able to type "/window 31¶" in dasher just now. It is quite hard to find the paragraph mark, it really wants you to go for the space, the paragraph is just above the space symbol if you zoom in far enough it appears. The training data at http://www.inference.phy.cam.ac.uk/dasher/download/training/training_english_GB.txt does not appear to have any paragraph marks following just numbers which might help make it a bit of a bigger target.

Revision history for this message
Alan Bell (alanbell) wrote :

yup, just tweaking the training data helps. I added the following to the end of the training_english_GB.txt file and it gets a lot easier:

some extra bits here to help working with IRC windows
/win 1
/window 2
/join #ubuntu
3
4
5
6
7
8
9
0

Revision history for this message
Patrick Welche (prlw1) wrote :

As you have found out, English text tends not to contain strings like \win 1\para, so adding such strings to your training text helps. Having "Language model adapts as you write" turned on and writing such strings teaches dasher about them. And another option is to try a higher value for "smoothing" (also on the "Language" tab in preferences). A higher "smoothing" value reduces the strength of the predictions, so low probability symbols such as the Paragraph symbol end up being allocated a higher probability than they deserve.

(Anyway, this isn't really a dasher bug as such, so in the strict "bug" sense, can be closed...)

Revision history for this message
Paul Sladen (sladen) wrote :

Where is dasher getting its initial seed training from in a default Ubuntu install? Is so, can be amend/append this so that people trying to use it have a better out-of-the-box experience. (This bug was reported to me in-person and verbally by somebody).

description: updated
Revision history for this message
Alan Bell (alanbell) wrote :

the initial seed training is in the file Data/training/training_english_GB.txt
I am unsure of whether the other language files should get the same text added, they seem to be rather different, not just translations, but each is a separate corpus of text from the given language.

Revision history for this message
Alan Bell (alanbell) wrote :

I am pushing a fix up to lp:~alanbell/dasher/bugfix-lp-579181

Revision history for this message
Alan Bell (alanbell) wrote :
Changed in dasher:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Stefano Rivera (stefanor) wrote :

Unsubscribing sponsors, as there is nothing for us to sponsor right now.

Alan: Please have a try at getting this fixed upstream. We try not to diverge from Debian unnecessarily. If we got closer to freeze and it hasn't been fixed yet, then provide a debdiff / bzr proposal and we can patch this into Ubuntu's dasher.

Alan Bell (alanbell)
tags: added: patch-forwarded-upstream
Changed in dasher (Ubuntu):
status: Confirmed → Triaged
tags: added: a11y
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.