oxcelix 0.3.1 → 0.3.2

data/CHANGES

@@ -1,3 +1,9 @@
+0.3.2
+* The numeric method in numformats will now try to gsub the correct format value and not the format index.
+* Required rubyzip version number is now >=1.1.0. 0.9.9 which was apparently 
+  enough did not load - thanks to Fredrik Persen Fostvedt for spotting that out.
+* Clarification added to the readme: Thanks again to Fredrik!
+
 0.3.1
 * Sheet now has its very own to_ru and to_fmt methods. Also a to_m method has been added, which returns a Matrix of raw data.
 * Documentation changes.

data/README.md

@@ -35,6 +35,7 @@ Synopsis
     `w = Oxcelix::Workbook.new('whatever.xlsx', :copymerge => true)`
   
   Convert a Sheet object into a collection of ruby values or formatted ruby strings:
+  
     `require 'oxcelix'`
     `w = Oxcelix::Workbook.new('whatever.xlsx', :copymerge => true)`
     `w.sheets[0].to_ru # returns a Matrix of DateTime, Integer, etc objects`
@@ -49,20 +50,14 @@ Installation
 Advantages over other Excel parsers
 -----------------------------------
 
-Excel file processing involves XML document parsing. Usually, this is achieved by some XML library such as Nokogiri[http://nokogiri.org].
-
-
-The main drawbacks of this approach are memory usage and speed. The resulting object tree will be roughly as big
-as the original file, and during the parsing, they will both be stored in the memory, which can
-cause quite some complications when processing huge files. Also, interpreting every bit of an excel spreadsheet
-will slow down unnecessarily the process, if we only need the data stored in that file.
-
-
-The solution for the memory-consumption problem is SAX stream parsing.
+Excel file processing involves XML document parsing. Usually, this is achieved by DOM-parsing the data with a suitable XML library.
 
+The main drawbacks of this approach are memory usage and speed. The resulting object tree will be roughly as big as the original file, and during the parsing, they will both be stored in the memory, which can cause quite some complications when processing huge files. Also, interpreting every bit of an excel spreadsheet will slow down unnecessarily the process, if we only need the data stored in that file.
 
-Oxcelix uses the SAX parser offered by Peter Ohler's Ox gem. Ox is fast and powerful enough to solve the speed issue.
+The solution for the memory-consumption problem is SAX stream parsing. This ensures that only the relevant XML elements get processed, 
+without having to load the whole XML file in memory.
 
+Oxcelix uses the SAX parser offered by Peter Ohler's Ox gem. I found Ox SAX parser quite fast, so to further speed up the parsing.
 
 For a comparison of XML parsers, please consult the Ox homepage[http://www.ohler.com/dev/xml_with_ruby/xml_with_ruby.html].
 
@@ -72,4 +67,4 @@ TODO
   * include/exclude mechanism should extend to cell areas inside Sheet objects
   * Possible speedups
   * Further improvement to the formatting algorithms. Theoretically, to_fmt should be able to
-    split conditional-formatting strings and to display e.g. thousands separated number strings
+    split conditional-formatting strings and to display e.g. thousands separated number strings

data/README.rdoc

@@ -42,20 +42,15 @@ Convert a Sheet object into a collection of ruby values or formatted ruby string
   gem install oxcelix
 
 == Advantages over other Excel parsers
-Excel file processing involves XML document parsing. Usually, this is achieved by some XML library such as Nokogiri[http://nokogiri.org].
 
+Excel file processing involves XML document parsing. Usually, this is achieved by DOM-parsing the data with a suitable XML library.
 
-The main drawbacks of this approach are memory usage and speed. The resulting object tree will be roughly as big
-as the original file, and during the parsing, they will both be stored in the memory, which can
-cause quite some complications when processing huge files. Also, interpreting every bit of an excel spreadsheet
-will slow down unnecessarily the process, if we only need the data stored in that file.
+The main drawbacks of this approach are memory usage and speed. The resulting object tree will be roughly as big as the original file, and during the parsing, they will both be stored in the memory, which can cause quite some complications when processing huge files. Also, interpreting every bit of an excel spreadsheet will slow down unnecessarily the process, if we only need the data stored in that file.
 
+The solution for the memory-consumption problem is SAX stream parsing. This ensures that only the relevant XML elements get processed, 
+without having to load the whole XML file in memory.
 
-The solution for the memory-consumption problem is SAX stream parsing.
-
-
-Oxcelix uses the SAX parser offered by Peter Ohler's Ox gem. Ox is fast and powerful enough to solve the speed issue.
-
+Oxcelix uses the SAX parser offered by Peter Ohler's Ox gem. I found Ox SAX parser quite fast, so to further speed up the parsing.
 
 For a comparison of XML parsers, please consult the Ox homepage[http://www.ohler.com/dev/xml_with_ruby/xml_with_ruby.html].
 

data/lib/oxcelix/numformats.rb

@@ -37,7 +37,7 @@ module Oxcelix
       # @return [String] a rubyish Kernel::Format string. 
       def numeric val
         ostring = "%"
-        strippedfmt = @numformat.gsub(/\?/, '0').gsub(',','')
+        strippedfmt = val.gsub(/\?/, '0').gsub(',','')
         prefix, decimals, sep, floats, expo, postfix=/(^[^\#0e].?)?([\#0]*)?(\.)?([\#0]*)?(e.?)?(.?[^\#0e]$)?/i.match(strippedfmt).captures
         ostring.prepend prefix.to_s
         if !decimals.nil? && decimals.size != 0

data/oxcelix.gemspec

@@ -3,8 +3,8 @@
 require 'rake'
 Gem::Specification.new do |s|
   s.name	= 'oxcelix'
-  s.version	= '0.3.1'
-  s.date	= '2013-12-07'
+  s.version	= '0.3.2'
+  s.date	= '2014-01-12'
   s.summary	= 'A fast Excel 2007/2010 file parser'
   s.description	= 'A fast Excel 2007/2010 (.xlsx) file parser that returns a collection of Matrix objects'
   s.authors	= 'Giovanni Biczo'
@@ -21,6 +21,6 @@ Gem::Specification.new do |s|
   s.license	= 'MIT'
   
   s.add_runtime_dependency "ox", [">= 2.0.6"]
-  s.add_runtime_dependency "rubyzip", [">= 0.9.9"]
+  s.add_runtime_dependency "rubyzip", [">= 1.1.0"]
   s.rdoc_options << '--all'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: oxcelix
 version: !ruby/object:Gem::Version
-  version: 0.3.1
+  version: 0.3.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-07 00:00:00.000000000 Z
+date: 2014-01-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ox
@@ -34,7 +34,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 0.9.9
+        version: 1.1.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -42,7 +42,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 0.9.9
+        version: 1.1.0
 description: A fast Excel 2007/2010 (.xlsx) file parser that returns a collection
   of Matrix objects
 email: