📊 Cross-platform user-friendly xlsx library for C++11+
Go to file
Xpol Wan c18110e282 add support for one cell with different formatted text nodes.
Eg, In one cell the text is abcdef, where abc and def have different format (e.g., different colours or fonts).
The the sharedString.xml in xlsx have multiple r node in si node:

```xml
    <si>
        <r>
            <t>abc</t>
        </r>
        <r>
            <rPr><sz val="10"/><color rgb="FFFF0000"/><rFont val="微软雅黑"/><charset val="134"/></rPr>
            <t>def</t>
        </r>
    </si>
```

Currently `shared_strings_serializer::read_shared_strings()` only reads the first r node, and should consider as a bug.

This commit fixes this bug by read all `r.t.text` values in one `si` node and concat the text into one single string.
2016-05-14 16:24:21 +08:00
benchmarks start porting benchmarks 2016-02-06 10:04:41 -05:00
cmake improve build 2016-01-16 21:07:02 -08:00
docs work on documentation 2015-11-03 18:26:33 -05:00
include/xlnt allow duplicate shared strings (why excel?). eventually we should do a garbage collection step that deduplicates shared strings after the workbook is loaded 2016-04-26 13:09:17 -04:00
samples add samples to be used in documentation and to be compiled 2015-11-10 19:16:50 -05:00
source add support for one cell with different formatted text nodes. 2016-05-14 16:24:21 +08:00
tests add support for one cell with different formatted text nodes. 2016-05-14 16:24:21 +08:00
third-party clean up styles and hashing, add license boilerplate to all files, update readme, finish moving implementations to source files 2015-12-24 15:51:11 -05:00
.clang-format fix formatting 2016-01-17 22:23:31 -08:00
.gitattributes initial commit 2014-05-06 17:28:38 -04:00
.gitignore fix all tests 2015-11-01 23:52:19 -05:00
.gitmodules clean up styles and hashing, add license boilerplate to all files, update readme, finish moving implementations to source files 2015-12-24 15:51:11 -05:00
.travis.yml fix travis 2016-01-16 21:33:15 -08:00
appveyor.yml improve build 2016-01-16 21:07:02 -08:00
AUTHORS.md start moving all implementations to source files 2015-11-19 22:54:54 -05:00
CMakeLists.txt improve build 2016-01-16 21:07:02 -08:00
CONTRIBUTING.md improve documentation 2016-01-17 20:11:51 -08:00
LICENCE.md start moving all implementations to source files 2015-11-19 22:54:54 -05:00
README.md Update README.md 2016-03-26 13:41:42 +08:00


Travis Build Status AppVeyor Build status Coveralls Coverage Status ReadTheDocs Documentation Status License

Introduction

xlnt is a C++14 library for reading, writing, and modifying XLSX files as described in ECMA 376. The API is based on openpyxl, a Python library to read/write Excel 2007 xlsx/xlsm files, and ultimately on PHPExcel, pure PHP library for reading and writing spreadsheet files upon which openpyxl was based. This project is still very much a work in progress, but the core development work is complete.

Usage

Including xlnt in your project

// with -std=c++14 -Ixlnt/include -Lxlnt/lib -lxlnt
// can also use the generated "xlnt.pc" in ./build directory with pkg-config to get these flags
#include <xlnt/xlnt.hpp>

Creating a new spreadsheet and saving it as book1.xlsx

xlnt::workbook wb;
xlnt::worksheet ws = wb.get_active_sheet();
ws.get_cell("A1").set_value(5);
ws.get_cell("B2").set_value("string data");
ws.get_cell("C3").set_formula("=RAND()");
ws.merge_cells("C3:C4");
ws.freeze_panes("B2");
wb.save("book1.xlsx");

Opening an existing spreadsheet, book2.xlsx, and printing all cells

xlnt::workbook wb2;
wb2.load("book2.xlsx");

// no need to use references, "cell", "range", and "worksheet" classes are only wrappers around pointers to memory in the workbook
for(auto row : wb2["sheet2"].rows())
{
    for(auto cell : row)
    {
        std::cout << cell << std::endl;
    }
}

Building

xlnt uses continous integration and passes all 200+ tests in GCC 4.9, VS2015, and Clang (using Apple LLVM 7.0).

Build configurations for Visual Studio 2015, GNU Make, and Xcode can be created using cmake and the cmake scripts in the project's cmake directory. To make this process easier, two python scripts are provided, configure and clean. configure will create build workspaces using the system's default cmake generator or the generator name provided as its first argument (more information on generators can be found here). Resulting build files can be found in the created directory "./build". The clean script simply removes ./bin, ./lib, and ./build directories. For Windows, two batch files, configure.bat and clean.bat, are wrappers around the correspnding scripts for convenience (can be double-clicked from Explorer).

Example Build (shared library by default):

./configure
cd build
make

Example Build, static library with tests:

./configure --enable-static --disable-shared --enable-tests
cd build
make

Dependencies

xlnt uses the following libraries, which are included in the source tree (all but miniz as git submodules) for convenience:

Documentation

More extensive documentation with examples can be found on Read The Docs.

License

xlnt is currently released to the public for free under the terms of the MIT License:

Copyright (c) 2015 Thomas Fussell

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.