Add options to set file type or embosser model, character table and page format

[bertfrees]

These options will be used in addition to output-file-format to determine the conversion from PEF to the final result. (Compare with how braille-code was split off from transform).

To specify the page format, several options might be needed. This information, together with the existing page-width and page-height options, will be used to determine the available rows and columns.

If both an absolute page size and a number of rows/columns (page-width and page-height) is specified, we try to respect the rows/columns setting if possible, and position the page on the physical page in an appropriate way.

If no information is given through options, the system could fall back to determining the page format based on the CSS (@page rules).

If needed, the CSS to OBFL conversion should adjust the formatting based on the printable page area for the given embosser (with warnings).

If the paper size has been computed from the specified number of rows and columns or from the CSS, this information should somehow be conveyed to the user (so that he can make sure the right paper is loaded in the printer).

[MDipendra]

Are we also considering various file formats as output files? Such as brf is one. E-braille should be added once it is finalized. We are also working on specifications for extension to brf to add navigation features in low cost braille displays that are not capable of parsing html or EPUB.

[bertfrees]

Are we also considering various file formats as output files?

Yes.

Such as brf is one.

I'm not sure yet I will call it "BRF". Because "BRF" is a term that does not mean the same everywhere, and conversely, in some regions they call the same kind of file format differently. Some more generic name might be more suitable.

E-braille should be added once it is finalized.

I agree. Perhaps it would be better to handle this on the UI level though, because the dtbook-to-pef script (even though the name is "DTBook to braille" in the user interface) is for paginated/embossed braille, in other words braille formats that can be derived from PEF. dtbook-to-ebraille will most likely be a different script because it's too different.

We are also working on specifications for extension to brf to add navigation features in low cost braille displays that are not capable of parsing html or EPUB.

Cool!

[MDipendra]

I feel we should choose one of the suitable and most acceptable definition of brf and provide as one of the output format. Brf as file format is most widely accessible. For example, most braille displays would support opening brf files directly. Almost every braille translation software supports export and import to brf.