Now I understand your headache. I felt that before when my application
needed to provide a lengthy manual in different languages. Eventually
I think "lengthy paragraph translating" is beyond the scope of any
"simple" i18n mechanism. So I decided to not bother the i18n, just
solve it via a raw way: prepare and maintain a manual_en.html and a
manual_bz.html and ... etc by human. Of course you can still "abuse"
the i18n mechanism to do the same thing, it works but merely
efficient: any slight change of source string forces you to re-
translate the whole paragraph again.
Sorry that my feedback doesn't provide any substantial help.