PocketExcel: try to also parse 1.0 files, ...
Pocket Excel: begin to add a parser to retrieve Pocket Excel files (last version)
WPSContentListener: add function to display basic shape,
PocketWord: try to parse some graphic's shapes, to be continued...
NEWS and configure.ac: update before release...
coverity: correct some warnings...
clang --analyze: correct some warnings
cppcheck: correct some warnings
Fix wrong Lotus version detection
update configure.ac to be compatible with autoconf 2.71
[BUG] [libwps Build Failed] Please consider updating autotool scripts.
Quattro Dos: try to retrieve correctly the spreadsheet's name when creating some
Quattro[dos,wq2]: try to retrieve sheet's name + check that the sheet id in formula
Home
Home
configure.ac: update minor before a release
cppcheck: try to remove some warnings, ...
configure.ac: add a --enable-asan option...
PocketWord: add possibility to reset the default encoding...
Add some PocketWord files + update the results...
Integration of unreleased but already committed patches had been a solved problem 10 years before git even existed. The proper way to do it is to include just the patch that's needed, not everything that's been pushed since the last release.
Possibility to downliad exact commit over http allows easy integrate with packaging systems when some unreleased but already commited patches needs to be integrated into generate packages.
migrate git repo to gitlab or github
Anyway, we're not going to move the project--and cause needless work for all downstreams--just based on a single request...
And why do you need this? Contrary to most github projects, we do have this thing called releases (with accompanying tarballs).
As well it does not provide automatic informing about new tags/releases (from that point of view I would choose github)
migrate git repo to gitlab or github
Pocket Word: activate this parser in release mode...
Pocket Word: begin to retrieve text (in debug mode)...
Pocket Word: begin to add a parser, to be continued...
Home
libwps[references]: add some XYWrite test files (mainly crap ones :-~)
coverity: correct many warnings
cppcheck: remove some warnings...
clang: correct a warning...
XYWrite.cpp: silent a g++ warning
g++: correct some warnings...
XYWrite.cpp: astyle + minor modifications...
XYWrite: try to retrieve some notes, ...
XYWrite: try to retrieve some frames...
XYWrite: try to retrieve more styles...
XYWrite: try to retrieve some basic counters,
XYWrite: try to retrieve some numbering lists...
Try to retrieve some styles...
XYWrite: try to retrieve some tables...
XYWrite: try to retrieve the headers/footers...
XYWrite[v1-4]: add code to retrieve basic commands...
Avoid accessing static members through instance
These can be static
These can be const
Multiplan: mark overriding function as such
Use auto when initializing with a cast to avoid duplication
Use range-based for loops
WKS4Spreadsheet.cpp: simplify the code...
I have commited some changes, I suppose that there will fix most problems...
wks,wk1: do not change the maximum number of columns...
wks,wk1,...: try to read correctly the row cell's references...
I just have commit a quick patch (which allows to reference relative row between 1 and 2048). This must fix the given bug for TEST3.WK1 and do not break my test files (in fact, this repairs 5 conversions). Note: I must relaunch my virtual machines to check what is the maximum numbers of allowed rows in wk1, wks(dos), ... because I suppose that it is not 256 :-~
lotus[wb1]: try to correct the retrieving of row references in formula...
Hello, I must take a closer look, but this patch seems to break a lot of formula in wb1 files ; so either we find a most robust way to know if a file is a wk1 or a wk3 file, or we have to choose between breaking many .wk1 formula or the .wk3 formula which contain reference to a cell with a column greater than 256 :-~
Hello, I must take a closer look, but this patch seems to break a lot of formula in wb1 files ; so either we find a most robust way to know if a file is a wk1 or a wk3 file, or we have to choose between breaking many .wk1 formula or the .wk3 formula which contain reference to a cell with a column greater than 256 :-~
Hello, I must take a closer look, but this patch seems to break a lot of formula in wb1 files ; so either we find a most robust way to know if a file is a wk1 or a wk3 file, or we have to choose between breaking many .wk1 formula or the .wk3 formula which contain reference to a cell with a column greater than 256 :-~
This looks sane to me. Alonso: do you have any further comments? Miklos
This looks sane to me. Alonso: do you have any further comments?
Fix wrong Lotus version detection
Make comparison operator member functions const
Make comparison operator member functions const
Thanks. Note: I just apply it, https://sourceforge.net/p/libwps/code/ci/9738ed97b10d5671b5e70f2c8149fe8f7949bce4/
Make comparison operator member functions const
Make comparison operator member functions const
Fix too small loop variables
Home
.wk3,.123: : add code to call the new detection function if encoding is unknown...
.wps: try to use OEM code in wps v1 + add code to call the new
Add some qpw X9 files...
update test results...
encoding: begin to add some detection functions,
.wb*: add code to call the new detection function if encoding is unknown...
.wk1/.wks/.wdb: add code to call the new detection function if encoding is unknown...
.wq*: add code to call the new detection function if encoding is unknown...
.doc,.wri: : add code to call the new detection function if encoding is unknown...
.qwp: add code to call the new detection function if encoding is unknown...
libwps_tools_win: simplify the code...
libicu: convert most encodings with libicu...
clang++: correct some warnings...