https://issues.apache.org/bugzilla/show_bug.cgi?id=53984

          Priority: P2
            Bug ID: 53984
          Assignee: [email protected]
           Summary: RuntimeException: Unexpected record type
                    (org.apache.poi.hssf.record.ColumnInfoRecord)
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: [email protected]
          Hardware: PC
            Status: NEW
           Version: 3.8
         Component: HSSF
           Product: POI

I keep getting this exception in an application which parses excel files sent
to us.

It's because the file has one or more ColumnInfoRecord right after a row block.
Like this:
Offset=0x00008772(34674) recno=1873 sid=0x00FD size=0x000A(10)
[LABELSST]
    .row    = 0x00D2
    .col    = 0x0006
    .xfindex= 0x002A
  .sstIndex = 0x001D
[/LABELSST]

Offset=0x00008780(34688) recno=1874 sid=0x0201 size=0x0006(6)
[BLANK]
    row= 0x00D2
    col= 0x0007
    xf = 0x002A
[/BLANK]

Offset=0x0000878A(34698) recno=1875 sid=0x0201 size=0x0006(6)
[BLANK]

... several empty cells in row 0xD3

[/BLANK]


Offset=0x000087D0(34768) recno=1882 sid=0x007D size=0x000B(11)
[COLINFO]
  colfirst = 0
  collast  = 0
  colwidth = 10240
  xfindex  = 0
  options  = 0x0000
    hidden   = false
    olevel   = 0
    collapsed= false
[/COLINFO]


Several versions of Excel and LibreOffice 3.5.4.2 open these files without
problem.
I don't know how they are generated, but I wonder if the record order described
in the OOO excelfileformat.pdf is strict or it is allowed for a
ColumnInfoRecord to appear after a row block.
Also I would like to know if the solution is as simple as adding
ColumnInfoRecord to RecordOrderer.isEndOfRowBlock which I guess was the
solution to a very similar bug (bug 50426)

Thank you very much.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to