Commit Graph

9 Commits

Author SHA1 Message Date
972897c9ae version bump 0.5.1: field reorg
- cell.r holds the raw rich text, cell.h now holds the html
  (version 0.5.0 cell.raw -> cell.r, cell.r -> cell.h)
- similar changes to comments and XLSB generation
- removed some unused binary methods
2014-02-05 08:39:21 -05:00
32d835ab81 version bump 0.4.0: very basic XLSB support
subfiles reshuffled (XLSB and XLSX/XLSM content separated)
2014-01-28 11:38:02 -05:00
9c9aad5df3 version bump 0.3.9: general format used by default
(when no format or style is found, use general)

Other whitespace cleanup
2014-01-23 11:14:11 -05:00
a1ccaf511d version bump 0.3.8: more formatting
- updated SSF to 0.5.3

tests without baselines now try to generate CSV output
2014-01-23 01:20:19 -05:00
Hugues Malphettes
5d43dffc79 Share the code for parsing the rich text and use it to parse the comments. 2014-01-18 21:45:49 +08:00
kinwah
80a843ca3b Add parsing comment codes into bits/70_xlsx.js
Update test xlsx file to apachepoi_SimpleWithComments.xlsx
2014-01-16 11:42:25 +08:00
kinwah
59d9d9086b Support for parsing Comments
Comments parts listed in the [Content Types] are parsed.
Sheets's relationships are parsed.
Comments parts are correlated to their corresponding sheets parts.
Comments's contents are added to the ref'ed cells.
Rich text styling properties are currently ignored.

For example:
{
  "!ref": "A1:B3",
  "A1": {
    "v": 1,
    "t": "n"
  },
  "B1": {
    "v": "one",
    "t": "s",
    "r": "one",
    "c": [
      { "a": "Yegor Kozlov",
       "t": [ "Yegor Kozlov:",
              "\r\nfirst cell" ]
      }
    ]
  }
}
2014-01-16 10:30:01 +08:00
afc4e281af version bump 0.3.5: updating SSF
- updated sheetnames tests
- updated ssf
2013-12-26 22:15:16 -05:00
713f5aa417 version bump 0.3.0: necessary cleanup
- merged test repo with xls
- travis integration
- shifted to Apache 2.0 LICENSE
- mocha tests

The shift to Apache 2.0 was long overdue.  It's becoming clear that compliance
requires deeper integration with the xls libraries and other implementations
whose specifications are covered under the OSP.  It was a grave oversight for
the ISO and ECMA people to not try to implement parsers themselves, for if they
did I suspect the outcome would have been much different
2013-10-30 14:50:34 -07:00