The OpenType codepath handles positioning completely differently than the fixed cell codepath (margins in pixels, instead of row/col +/- pixels).
As such, some of the more esoteric features available w/ cell rendering aren't supported. Padding (left or right) happens to be one of those things
.
(The
API documentation for print_ot should have the exact list of supported settings. The CLI tool's help message has a
matching "Honor <such and such> flags" line, too).
Font metrics and weird (and not so weird) corner-cass being what they are, what you're asking for is actually slightly tricky to reliably compute *without* rendering the line first. Especially with non-monospaced fonts
. (Conversely, it's fairly trivial with fixed-cell, because we know the absolute amount of cells in a line, and that every glyph will fit in one, and that every cell will have the same size).
Depending on what exactly you're doing, the easiest workarounds would be adding a few blank spaces on the edges and/or playing with the margins.
(i.e., unless you're in backgroundless mode, the full drawing area will be background-colored, preventing overlaps if you're reusing the same margins (EDIT: Nope, that was a lie ^^)).
You can probably fine-tune the amount of padding needed via the "compute" feature, which will report the amount of lines that would have been printed, and whether it had to be truncated. While the --coordinates flag will report the actual bounding box of the whole thing.