[brailleblaster] Re: UTD Styles
- From: "Keith Creasy" <kcreasy@xxxxxxxxx>
- To: <brailleblaster@xxxxxxxxxxxxx>
- Date: Mon, 8 Dec 2014 15:47:24 -0500
It could be. I'm not sure exactly how that would work. Do we need anything
else for managing graphics?
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Yuemei Sun
Sent: Monday, December 08, 2014 3:45 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: UTD Styles
Is the option "format <block, inline, tabular>" for specifying table as well
as reserving spaces for graphics?
Thank you,
Yuemei
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Keith Creasy
Sent: Monday, December 08, 2014 6:02 AM
To: brailleblaster@xxxxxxxxxxxxx; brailleblaster-dev@xxxxxxxxxxxx
Subject: [brailleblaster] UTD Styles
All.
I'm going to throw this out for the entire group. We are working on a new
UTD Library that is XML-centric for both input and output. We are at the
point of implementing styles. Mostly the styles are going to be handled
using the same options as the current LibLouisUTDML library.
Here are the current options with a couple of changes as a starting point:
linesBefore int
linesAfter int
leftMargin int
firstLineIndent int
#translationTable <a table name>
skipNumberLines <no, yes>
format <block, inline, tabular>
align<leftJustified, rightJustified, centered, computerCoded,
alignColumnsLeft, alignColumnsRight, contents>
newPageBefore <no, yes>
newPageAfter <no, yes>
righthandPage <no, yes>
braillePageNumberFormat <normal, roman, p, blank>
keepWithNext <no, yes>
keepWithPrevious <no, yes>
dontSplit <no/yes>
orphanControl int
newlineAfter <yes, no> # do we really need this? Could be
done using block, linesAfter.
topBoxLine <char>
bottomBoxLine <char>
We need to think carefully about how we are going to do boxed text.
Currently we have styles for boxline, topBoxLine, midBoxLine, bottomBoxLine,
and fullBoxLine. They work well enough but in the style we define the
character for the top and bottom boxline for each box style. The character
should probably be defined in the LibLouis tables, or at least one could
argue for that.
This is your chance to suggest additions, changes or corrections before we
start to implement all the options for styles. BTW, the style options are
going to be implemented in a very similar way to "actions". Each action or
style option has it's own class and implementation. This should make adding
and debugging them pretty easy.
Other related posts:
