This is a long answer to explain that, if you have a hybrid form, it is in most cases OK to throw away the XFA part. Hence if you have text that is justified in an XFA form, but you only look at the AcroForm, then the text won't be justified (because justified text doesn't exist in an AcroForm text field). However, this option doesn't exist in an AcroForm text field (you can only have left, center or right alignment). For instance: a text field in an XFA form can be justified (similar to in HTML). XFA has more functionality that AcroForm technology.If the form isn't filled out correctly, the AcroForm can be different from the XFA form.Ideally, both versions of the form are indeed equivalent, but:

What's the problem, you might ask? Aren't both forms equivalent? A viewer that is XFA aware, can give preference to the data as stored in the XFA form. For instance: a viewer that is not XFA aware, will show you the data as stored in the AcroForm. Hybrid forms are a pain because they often lead to confusion. However, it seems that you are confronted with a hybrid form that consists of both AcroForm and XFA syntax. If you have a dynamic XFA form, dropping the XML will remove the complete form.

Obviously, such a form is not dynamic: the AcroForm part still defines widget annotations that are defined at absolute positions on specific pages. In this case, the form is described twice: once using PDF objects once using XML. Hybrid forms that combine AcroForm and XFA technology.We refer to this as dynamic XFA, because the form can expand or shrink based on the data that is added: a 1-page form can turn into a 100-page form by adding more data. In this case, the PDF file is nothing but a container for an XML file that describes the whole form. Dynamic forms using the XML Forms Architecture (XFA).The form is described using nothing but PDF syntax. In this case, each field corresponds with one or more widgets with fixed positions on specific pages.

Adobe acrobat pro dc ubuntu