[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-10-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 Dominik Stadler changed: What|Removed |Added Blocks||46136 --

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-03-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 Dominik Stadler changed: What|Removed |Added Blocks||58641 --

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-02-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 Nick Burch changed: What|Removed |Added Resolution|--- |FIXED

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-02-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 Nick Burch changed: What|Removed |Added Status|NEW |NEEDINFO ---

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-01-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #6 from Nick Burch --- For the HSSF stuff, look at FeatFormulaErr2 Looks at first glance like the list is almost the same. Assuming that's really the case, it'd probably be best to put the IgnoredErrorType

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-01-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 Dominik Stadler changed: What|Removed |Added Severity|normal |enhancement

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-01-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #4 from David North --- Excel supports multiple ignoredError elements. Furthermore, the flags on each one are not mutually exclusive, so if a given cell range has the same error(s) they can be

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-01-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #5 from David North --- I've checked in an attempt at a generalised API in SVN r1724469 Nick, is that approximately what you had in mind? Whether this can be generalised to cover HSSF too is best

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2016-01-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 David North changed: What|Removed |Added Status|NEEDINFO|NEW --

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2015-06-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 quen...@yahoo.fr changed: What|Removed |Added CC||quen...@yahoo.fr -- You are

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2015-06-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #3 from David North dtn-asfb...@corefiling.co.uk --- See also bug 54868, bug 46136 -- You are receiving this mail because: You are the assignee for the bug. - To

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2014-08-30 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56892 Dominik Stadler dominik.stad...@gmx.at changed: What|Removed |Added Status|NEW |NEEDINFO

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2014-08-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #1 from Chris Boyle cmb-apa...@corefiling.co.uk --- Created attachment 31948 -- https://issues.apache.org/bugzilla/attachment.cgi?id=31948action=edit Patch to add XSSFSheet.addNumberStoredAsTextIgnoredError The attached patch

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

2014-08-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #2 from Nick Burch apa...@gagravarr.org --- Thanks for this Looking at the code and unit test, I wonder if it might be worth making it a bit more general? For example, define an enum of the kinds of errors that can be ignored