Recent changes to bugs-rcp

Blocking conversion for missing alttext/altimg for MathML

Christophe Strobbe — Tue, 24 Aug 2010 16:09:27 -0000

In odt2daisy, the DAISY Pipeline Lite stops the conversion of ODT documents with math content because of missing alttext and altimg; users are advised to buy and install MathDaisy from Design Science. This should not be a requirement: instead of blocking the conversion, users should get a warning and be given the option to continue, so they can fix the accessibility issue in the exported DAISY book.

DTBOOK not converted to ePub

Anonymous — Sat, 06 Mar 2010 05:49:49 -0000

Hi, I am using Daisy Pipeline GUI 1.0 convertor for converting my DTBOOK xml file to ePub. The problem is that it is running continuously for a long time (approx. 6 - 7 hrs) and not able to convert that xml file. I have already tested the same software by converting an another xml file to epub and it convert successfully. Can anybody please let me know the possible problem with that convertor? My xml file is a valid file conformant to DTBOOK 2005-2 DTD. Your quick reply will be helpful.

Thanks,
Naushad

Arrow Up/Down cycle the tasks in the Progress view

Romain Deltour — Mon, 20 Aug 2007 08:35:43 -0000

While navigating the task list in the progress view with arrow down (resp. up), if we reach the end (resp. beginning) of the list then the selection cycles to the beginning (reps. end) of the list.

This behaviour should be changed: it shouldn't cycle but stop when the top/bottom item is reached.

[ACCESS] Header widget of progress view isn\'t spoken by SR

Romain Deltour — Mon, 20 Aug 2007 08:31:32 -0000

The header widget of the progress view, which has info on the displayed Job and ellapsed time, is currently spoken as a "custom control" by screen readers.

Investigate on how to call the accessbility API.

[ACCESS] ToC title is not spoken by SR after Ctrl+TAB

Romain Deltour — Mon, 20 Aug 2007 08:12:42 -0000

When using Ctrl+TAB to cycle through the documentation tabs (*Help*, *Scripts* and *Transformers* table of contents), the tab title is not spoken by the screen reader, making it non-obvious to the user that the focus changed and what the new ToC is.

We should try to catch the Ctrl+TAB event and directly call the accessibility API.

[ACCESS] Show next view action doesn\'t cycle the views

Romain Deltour — Mon, 20 Aug 2007 07:59:00 -0000

The 'show next/previous view' actions (accessible via Ctrl+F7 on Windows or Cmd+F7 on Mac) does not cycle through all the existing views but only the two most recently used views.

This action comes from RCP. It should be investigated wether it's fixable as is or it requires a new action to be written (+ report to Eclipse).

[ACCESS] parameter nodes don\'t have right Accessible label

Romain Deltour — Thu, 12 Jul 2007 07:59:02 -0000

In jobs view, the nodes of jobs tree do not have right Accessible label or you may say accessible names.
Description:
Create a narrator job.
Move to jobs tree in jobs view.
the first node displayed is narrator.
Expand this node.
now three nodes appear.
1. Source file.
2. Destination folder.
3. Bit rate of mp3 conversion.

But if I go for Accessible information for a these three nodes, I get back
"status:"
for all 3 expanded nodes.

Screenreaders which depend on embedded information are speaking "status" instead of correct text.

(quote of an email from Avneesh)

[ACCESS] Doc is not updated if ToC is changed via Ctrl+TAB

Romain Deltour — Tue, 10 Jul 2007 09:23:30 -0000

If the ToC tab is accessed via Ctrl+TAB, then selecting a doc item (with the arrows) does not upadte the browser widget.

A workaround is to switch the ToC tab by TABing through the tab control and selecting the tab with the arrows, instead of using Ctrl+TAB.

[ACCESS] Need a TAB after F6 to set the focus to the Browser

Romain Deltour — Tue, 10 Jul 2007 09:19:05 -0000

After pressing F6 to toggle to the Browser widget, the user needs to press an additional TAB key to give the focus to the browser widget.

Pressing F6 should directly set the focus to the Browser, and addtional TAB shouldn't be required.

Cannot change the value of a boolean script parameter in GUI

Joel Håkansson — Wed, 04 Jul 2007 11:21:02 -0000

Checkbox setting is not read in the GUI, the default value is always used.