New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quick question - strike-through font detection #19
Comments
Sorry for taking so long to answer. Also - the {includeEmpty:true} may not necessary as it will cause the eachCell to include empty cells as well as ones with values. |
Awesome. Thanks for the reply and for the suggestions -- I had already forgotten about this, so you just gave me a nice incentive to go build my test harness. Much appreciated! |
@guyonroche , thanks again for your module, it is working well for me detecting (and ignoring) strike-through text in cells. I found your module very easy to work with too, great documentation. I have a lot of refactoring in my future to consolidate some of my existing row/col/cell brute-force operations to take advantage of some methods in your module, which were not available in the module I was using previously. However, I found out that there are 4 use cases I need to handle, where the cell contains a mixture of strike-thru and non-strike-thru text, and currently I'm only catching 2 of those use cases (up to the first occurrence of strike in the cell). Any thoughts on how to handle this?
|
I have been looking around for an xlsx parser that can detect strikethrough and other font properties. Your module looks quite excellent, but I have not had a chance to clone your repo and mock up a test case, so I've decided to ask a question here instead... I'm looking at your examples and seeing the .font property being used as a setter for getCell()... Can I read an existing XLSX and access the existing cell font properties by doing something like the following?
Many thanks in advance for taking the time to answer a question!
The text was updated successfully, but these errors were encountered: