You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When coding Django's tags via LibreOffice window, we are practically unable to control the way LibreOffice stores them in its messy zipped od* archive. One may happen that Django's tags are messed up with xml tags as shown below:
<text:ptext:style-name="P21">Lorem ipsum {{
<text:spantext:style-name="T12">element.el0 }</text:span>}
<text:spantext:style-name="T12">and {{ element.el1 }} and {{ element.el2 }} and </text:span>{{
<text:spantext:style-name="T12">element.eln }</text:span>}
</text:p>
So templated-docs unzips template and Django replaces its tags with data. But how it works with markup like this }</text:span>}? Obviously, source xml will be broken and, furthermore, od* corrupted.
Thanks for comment @danilogbotelho. Issue persists with ODF fields too. And actually I see no reason why it should not. As document is getting more complicated, sooner or later you will unfortunately face the issue.
When coding Django's tags via LibreOffice window, we are practically unable to control the way LibreOffice stores them in its messy zipped
od*
archive. One may happen that Django's tags are messed up withxml
tags as shown below:So
templated-docs
unzips template and Django replaces its tags with data. But how it works with markup like this}</text:span>}
? Obviously, sourcexml
will be broken and, furthermore,od*
corrupted.Maybe here is the explanation of the issue #8
I don't know if there's any way to fix the issue except programming source
xml
.The text was updated successfully, but these errors were encountered: