on the PDF output page 1 the text description for the barbarian rage (with the checkboxes for 'per day' usage) extends outside the box for the Rage section and continues far to the right off the edge of the page.
Uses per day ❏❏❏❏
The Barbarian gains +4 to Strength, +4 to Constitution, and a +2 morale bonus on Will saves, but suffers a -0 penalty to AC for 7 rounds. At the end of the rage, the barbarian is fatigued
I cannot find this text defined anywhere in the .LST data, however it does appear in the temporary output .xml that is fed into the xlst as below. I thought it was my homebrew DESC affecting this, however this appears to be hard coded?!
<!-- If character can Rage -->
<uses_per_day.title>Uses per day</uses_per_day.title>
<description>The Barbarian gains +4 to Strength, +4 to Constitution, and a +2 morale bonus on Will saves, but suffers a -0 penalty to AC for 7 rounds. At the end of the rage, the barbarian is fatigued (-2 to Strength, -2 to Dexterity, can't charge or run) for the duration of that encounter. The barbarian can only rage once per encounter. Entering a rage takes no time itself, but the barbarian can only do it during his action.</description>
I do so love assumptions. Just makes my day.
I've wasted a few minutes reading all of this trying to decipher WHAT THE ACTUAL ISSUE IS.
Is the duration wrong, or is the text wrapping, or are we talking about hard coded outputs? As a developer, looking at a SINGLE ticket request I can't make heads or tails of this report. Seems to rambling about too many things and not informative about the ONE issue it should be focused on. Anyways, since I can't figure out the real issue you want addressed, and I spent my few free minutes available to let you know I don't know what you want, I'm going to now go deal with my higher priority school work.
Please update this issue, and or make separate issues so you aren't confusing the limited pool of volunteers who have very little time to address things.
Split bug into two.
This issue is with the PDF output sheet not wrapping text for the Barbarian rage detail on the first page of the OS.
Apologies for the lack of clarity on the original bug.
can you investigate the text wrapping issue when you have a moment, this would a 3rd edition style character using the more/or less hardcoded text in the class features common block. Personally, we should move to using the output text in the description and bypass hardcoded values, but i have neither the time nor energy to commit to a clean up like that.