I noticed that several of these test files have several oddities (you might
want to talk to Klass Bals at InventiveDesigners about these):

  1.) text-decoration=" no-line-through no-underline"
        The space after the opening quote is technically not legal,
      but more important is the question of whether it was intended
      to be:
          text-decoration="overline no-line-through no-underline"

  2.) text-style="bold"
        This property sets italic|oblique|normal; you should use
      font-weight="bold".

  3.) A lot (possibly all) of the fo:block elements are a nested pair
      or are a series of inner blocks within an outer one:
        <fo:block space-before="0.0pt" padding="2.0pt"
                  margin-right="0.0pt" margin-left="0.0pt" 
                  border-width="0.0pt 0.0pt 0.0pt 0.0pt" 
                  border-style="solid solid solid solid" 
                  border-color="#990099 #990099 #990099 #990099"
                  background-color="#ffffff"
        >
            <fo:block
                 text-align="center"
                 font-size="8.0pt"
            ><fo:inline 
                     white-space-collapse="false" 
                     text-decoration=" no-line-through no-underline" 
                     font-weight="bold" font-style="italic" 
                     font-size="8.0pt" font-family="Arial" 
                     color="#000000"
                >REFERRALS &amp; SALES</fo:inline></fo:block></fo:block>

  4.) There is not a single line-feed (CR/LF) in the entire file. This
makes the files hard to re-edit using normal text editing tools. Two
standard text editors crashed, one arbitrarily broke the file into ~2k
chunks, sticking in LFs willy-nilly (in mid-parameter or mid-word most of
the time).
    

On other issues:
  1.) Our product does not process background-color, borders, nor padding
on normal blocks and inlines. Some of these I can make into
inline-containers or block-containers, but not all.
  2.) We do not support nested tables. I will look at if I can linearize
these.
  3.) We do not support absolute-position="absolute" (except on region-body
as an extension). I'll see if these can be positioned using float,
block-container, or tables.
  4.) We support only one page-sequence per document (in this release,
since our intent was to use FO to produce short financial reports,
insurance forms and stock-broker reports; not to use it for producing
tech-pubs). I'll split these into separate docs.
  5.) Your large file runs out of memory (as you probably accepted). I will
retest this on fully configured server, but do not plan to waste the time
to edit the file down to see how large a file we can process.
  6.) Our product requires explicit (specified as a length, not "auto")
height & width on all containers (float, block-container,
inline-container); and explicit height, width, content-height, &
content-width (specified as a length, not derived from the content) on
instream-foreign-object and on external-graphic. I'll replace the
non-length values with lengths, as necessary.
  7.) We also don't support percentages, where the percentage is derived
form the containing region or column, since these cant be evaluated when we
convert FO to the language of our current formatter. I will choose an
appropriate length for these values.