#13 Chars returned in "wrong" box when word flows across boxes

[Tad Woods]

In most of the Acord 125 applications, under the General
Information section, the "X"s are correctly returned in
boxes aligned under the Yes/No columns corresponding
to the applicant's Yes/No answer.

Some implementations of the application, such as
Plastic Solutions, apparently implement "No" by printing
a " X" (space-X) under the "yes" column. In this case the
space begins in the "yes" column but the "X" physically
crosses the boundary of the box into the "no" column.
PdfToXml returns this case as " X" in the box aligned
with the "yes" column; I would prefer that it split the
word at the box boundary and return " " in the box
aligned with "yes" and "X" in the box aligned with "no".
However I am open to discussion as I realize this may
be difficult.

Example of the Yes/No boxes and a "no" answer in the
Plastic Solutions application:

<BOX x1="281" y1="277" x2="295" y2="263">
<TEXT x="282" y="270">
<FONT face="Arial" style="font-size:6pt;font-
style:Bold">YES</FONT>
</TEXT>
</BOX>
<BOX x1="296" y1="277" x2="309" y2="263">
<TEXT x="298" y="270">
<FONT face="Arial" style="font-size:6pt;font-
style:Bold">NO</FONT>
</TEXT>
</BOX>
<BOX x1="281" y1="264" x2="295" y2="251">
<TEXT x="285" y="261">
<FONT face="LucidaSansTypewriter" style="font-
size:9pt;font-style:Bold"> X</FONT>
</TEXT>
</BOX>

Same example in the Acutherm application:

<BOX x1="282" y1="257" x2="296" y2="245">
<TEXT x="282" y="254">
<FONT face="Arial" style="font-size:6pt;font-
style:Bold">YES</FONT>
</TEXT>
</BOX>
<BOX x1="297" y1="257" x2="310" y2="245">
<TEXT x="297" y="254">
<FONT face="Arial" style="font-size:6pt;font-
style:Bold">NO</FONT>
</TEXT>
</BOX>
<BOX x1="297" y1="246" x2="310" y2="233">
<TEXT x="303" y="243">
<FONT face="CourierNew" style="font-size:10pt;font-
style:Bold">X</FONT>
</TEXT>
</BOX>

[Douglas Sellers]

Logged In: YES
user_id=335059

Whatever pdf writer is doing the plastics pdf is a big
problem. It seems to try to intentionally try to work against
pdftoxml. That said the problem you described above is
fixable but it will be a very difficult fix that is probably going to
take a week or two to get done. My question to you would
be how pressing is this problem and are you willing to
sacrafice me working on all the rest of the bugs to fix this
one?

[Tad Woods]

Logged In: YES
user_id=722301

This problem should have the lowest priority among the
outstanding bugs.

[Tad Woods]

Logged In: YES
user_id=722301

The Syosset Seafood application exhibits the same behavior
as the Plastic Solutions application. This remains a low
priority because the parsing process can easily recognize
and compensate for this bug.