brailleapps / brailleutils Goto Github PK

- Basic-D V4
- Everest-D V4
- Braille Box

Add 8-dot support for the following embossers:

  - Braillo 400S
  - Index Basic V3
  - Index Everest V3

Paper orientation not supported. Support for paper orientation would be nice. 
Note that some embossers might support one direction, but not the other.

Workaround is to create a new paper with the width and height reversed.

Currently, the supported fallback methods are:
mask, replace, remove.

Add support for "fail" option as fallback method. If this method is chosen, an 
exception should be raised if a character in the 2840-28FF range is encountered.

What steps will reproduce the problem?
1. Run the validation with a file that has too long rows

What is the expected output?
An error message containing line number where the error occurred.

What do you see instead?
An error message without line number.

The implementation is dependent in a certain version of Jing, this may be 
possible to avoid, if the generic API is used instead. Look for thaiopensource 
packages, and see if they can be replaced by more generic interfaces.

Provide table option for embossers that require the user to select a table, for 
example Braillo embossers.

- Impacto Texto
- Impacto 600
- Portathiel Blue

Build.xml does not create all directories needed for a fresh check out to 
complete unit tests.

Check out project in a new workspace. Run unit tests in build.xml

.class files have been added to the repository. Remove these and add to 
svn.ignore

Support embosser index 4x4 pro

- BRF (Duxbury file format)
- BRL (MicroBraille file format)
- BRA (Braille file format common in Spain)

Support for unlimited paper (i.e. for file output) has been lost.

Two options are possible:
  * adding a paper with maximum width and height
  * add a special case which ignores paper settings

If this is a big issue, perhaps we could move back to Java 1.5

Add an option to emboss a range of pages through the BasicUI

Write tests for release 1.1.0 embossers to test with trunk version

What steps will reproduce the problem?
1. run PEF validator from UI with "mode" option

What is the expected output? What do you see instead?
"mode" option has no effect. 

Review design choices and fix possible problems

Move the splitter/merger functionality in Daisy Pipeline to this project

Remove previously deprecated methods (1.1.0)

Add support for Braillo 270 embosser

Set up a Google group for this project.

http://www.mountbattenbrailler.com/

= all Tiger printers

TextHandler should support setting max row and cols. As it is today, 
TextHandler might creates a PEF-file with very long rows and/or very long pages 
if, for example, the document does not contain any FF's.

If max row and cols were an option, row or page could be broken automatically, 
if exceeded. Or an exception could be thrown.

The TextParser UI is difficult to run, because the strings that the user has to 
enter in order to choose mode is too long.

Provide an interactive selection method or map the real value to a shorter one

Add licence and documentation to all java files

Printing fails. Document is sent to printer/embosser but it stays in the 
printer queue.

The Generic Embosser is also used for converting to text, this is a scope creep 
and should be supported some other way.

- Interpoint 55

Add support for Juliet embosser from Enabling Technologies 
(http://www.brailler.com/)

Enhance:
- Basic S/D
- Everest-D

Add:
- 4x4 Pro
- 4Waves Pro

What steps will reproduce the problem?
1. run java -jar brailleUtils.jar emboss -clear
2. run java -jar brailleUtils.jar emboss -setup

What is the expected output? What do you see instead?
The settings are still there as default values.

Please use labels and text to provide additional information.

Enhance:
- Index Basic S/D V2
- Index Everest V2

Add:
- Index 4x4 Pro V2

Add build target that zips the javadoc. The purpose is to provide an 
API-documentation download. Specifically for older releases.

Add OSGi support for braille utils

- Romeo Pro 50
- Juliet
- ...

- 3.7
- Advanced
- Basic Blue Bar
- Classic
- Domino
- Everest-S V1
- Everest-D V1

Sometimes it would be useful to be able to have optional arguments without 
value, such as:
-version
-setup

Currently, you have to set these as required arguments, which is contradicted 
by the optional argument prefix '-'.

"XxxCatalog" classes use the context class loader, which causes a problem when 
using BrailleUtils within OpenOffice.org: see also bug report at 
http://openoffice.org/bugzilla/show_bug.cgi?id=93740

If two tables are identical, the table detector should not worry about finding 
more than one match. It is safe to choose one of them.

The PEFParser UI is difficult to run, because the strings that the user has to 
enter in order to choose an embosser and a table is too long.

Provide an interactive selection method or map the real value to a shorter one

Support copies in EmbossPEF UI (and possibly in the Embosser interface)

There should be an option to verify (and change) settings and emboss in the 
same command, i.e.:

emboss path_to_file -setup

Only list papers that are supported by the selected embosser in the UI

Start the UI with parameters emboss -setup

Select an embosser that does not support all existing papers.

Note that the unsupported paper appears in the list.

Add an option to enable debugging.

If not set, only show the error message. If set, show the entire stack trace.

Check equals implementation in NumeralSortString, it does not override 
Object.equals.

It causes no problem at the moment, but it should be fixed, as it may cause 
confusion at some point.

Several additions to an earlier version of this code have been made in the 
odt2braille project. Reintegrate with this project in order to get a common 
base for embossing between Daisy Pipeline and Open Office.

Review naming convention of interfaces and classes in order for the design to 
be more transparent.

Determine if visibility should be reduced for "catalog" implementations (except 
for factory methods). For example, Braillo200Embosser has a public constructor, 
but should really only be called by its Provider. Therefore, package visibility 
should suffice.