Accepted, Not Yet Planned

We appreciate the additional information provided explaining how the current constraint impacts existing automated production workflows. We understand the request, but will need to research what it will take to make this change and if it will require a database rev of XPP or not. That research will impact when might be able to target this change. We are tracking this as XPP-11076 on the XPP Product Backlog.


Would you please each share with us the maximum number of characters you've had to accommodate to date, and that you envision needing to accommodate? Having this information will also help us determine next steps. For example, if we learn that we can increase the left-flush and right-hang fields each to 8 characters without revving the database, will that be enough to meet the alignment requirements or is that not worth doing because the requirement is 10?

Any additional information you can provide with real use case examples will be helpful.

Thank you!

In Tabular t4 table, left‐flush and right‐hang character alignment setting are limited to 4 characters, it is needed to be extended to handle more characters.

Simon Tung
Parents

  • Hello,

    This question has come up a few times very recently: "Why does the four-character limit exist in the t4 spec?

    The need to support additional f-left and r-h characters
    On our interactive system, we've relied on typesetters to key in the overrides necessary using <setaln> and <cal> to compensate for the limitation in the t4 spec. For some of our other offerings, there are no typesetters involved, this is the reason I've been asked the question above and if these fields could be expanded so that additional characters could be added. 

    While I know I can create additional rules in the t4 spec, having these rules trigger automatically in an automated environment isn't always possible.

    Adding the Simon's earlier request to extend the number of characters that can be entered into the f-left and r-h fields in a single t4 alignment rule.

    Kind regards
    Thomas


Comment

  • Hello,

    This question has come up a few times very recently: "Why does the four-character limit exist in the t4 spec?

    The need to support additional f-left and r-h characters
    On our interactive system, we've relied on typesetters to key in the overrides necessary using <setaln> and <cal> to compensate for the limitation in the t4 spec. For some of our other offerings, there are no typesetters involved, this is the reason I've been asked the question above and if these fields could be expanded so that additional characters could be added. 

    While I know I can create additional rules in the t4 spec, having these rules trigger automatically in an automated environment isn't always possible.

    Adding the Simon's earlier request to extend the number of characters that can be entered into the f-left and r-h fields in a single t4 alignment rule.

    Kind regards
    Thomas


Children