Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: configurable width of columns #6

Open
heiderich opened this issue Sep 6, 2017 · 2 comments
Open

Feature request: configurable width of columns #6

heiderich opened this issue Sep 6, 2017 · 2 comments

Comments

@heiderich
Copy link

It would be nice if the width of each column corresponding to a choice entry within choicegroup would be configurable in LaTeX.

@benzea
Copy link
Member

benzea commented Sep 7, 2017

I think the idea would be to change the cell typesetting from using an hbox to using a vbox. The requirement for this to happen would be that a keyword argument with the width has been given somewhere.

Notes:

  • It is a column width, so the setting will need to be together with the surrounding environment
  • Internally we will need a second cell layout function when typesetting to a certain width (similar to row header typsetting)
  • Main difference to row headers is that content should be centred by default.
  • The magic to detect the top/bottom baseline needs to be improved to also handle cells.
  • Decision on how to layout the cells/row header against each other when they are multi-line. Maybe:
    • Match top baseline on all cells
    • Centre the cells to the row header (i.e. align the midpoints of the top/bottom baselines)

This probably changes the current layout in some circumstances, but that is fine at this point. Overall, should be very much doable.

@benzea
Copy link
Member

benzea commented Sep 7, 2017

Oh, I guess we might need to special case the header row. i.e. there it makes sense to align the bottom baseline of each header. Note that it is unlikely that we generally have multiline content in table cells in SDAPS, but it would still be nice to have a sane handling there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants