excelize VS excelize

Might have moved it from https://github.com/xuri/excelize? It redirects to qax-os :)

The repositry's URL has changed twice for some reason, there some change about the orgnization of my previoues company. I'm sorry for bringing you inconvenience. The original repo address (https://github.com/xuri/excelize) and go module name (github.com/xuri/excelize/v2) won't be changed.

Excelize (github.com/xuri/excelize) since 2016 has become the popular choice to process spreadsheets documents among cloud-native and especially among Go language developers. Deep in essence and known for their professional support and well capabilities, Excelize is being widely used by large Internet companies, SME customers, and startup companies. Now, for the 5th anniversary of the Excelize open source, it has been released 16 versions, more than 100 contributors have participated in code contributing. I would like to thank all those who support the development and contributions of the project, and I'm very happy to be able to help anyone in need it. For me personally, creating and maintaining an open-source project requires not only the ability to write code, write documentation, and community management, the more important thing is how to keep the enthusiasm, happy, energetic, and efficient output state.

A summary of changes is available in the Release Notes. A full list of changes is available in the changelog.

GitHub: github.com/xuri/excelize

Fix AddPicture autofit failure with multi merged cells, resolve issue #748

Then I found out that WPS only supports ecma376 standard encrytion for xlsx files. Then I referred to the official documentation and libraries in other languages, such as msoffcrypto-tool written in python. msoffcrypto-tool) and go's excelize. Since I don't know much about encryption and decryption, the process of implementation is also a bit of a twist.

But if you absolutely need xlsx files, I would seek the best library for the job and write this in golang.

Documentation website with multilingual: Arabic, German, Spanish, English, French, Russian, Chinese, Japanese, and Korean, which has been updated

Golang excel: https://github.com/qax-os/excelize

Yeah, I'm reading it now and just parse, I didn't find a implementation of "calculation engine" all the available libs just read previous saved value from a opened and calculated excel file. See: https://github.com/qax-os/excelize/issues/65

Hey guys, i tryed using this https://github.com/qax-os/excelize to read excel table ,(70+columns and 500k rows). When using the sheet method from the documentation it takes about 3 to 4 minuts to find search item, and ofcourse limitation is that it needs to be a match.

Much like excelize for go lang.

Suggestion: When a method is safe for concurrent use, document such in its godoc comment. None of the formal documentation mentions concurrency, and its unclear what methods are concurrency-safe. The only tip-off that something might be safe for concurrent use is the occasional use of the sync package. This eventually led me to a year-old release footnote as the only documentation across the entire project about concurrency. This information isn't even in the Git tag, just the GitHub release page.

The title more or less says it all, but to give some background to the question, as long as it’s done safely (for example, with a mutex and locks) like with concurrent writing to a txt file, does anyone know if concurrent writing to an excel file, particularly while using excelize/v2 is possible? I have a 2D slice of data produced after processing an image that needs to be written to an excel file created with excelize/v2 and it’s plenty fast up to a certain set of dimensions, but I’d like to support even larger dimensions and was considering using concurrency to do so. But the only examples of concurrently writing to a file with Go that I could find were txt file examples. So I’m not quite sure if my scenario is possible.

You’re unlikely to find a single package that will handle all these file types without being behind a paywall of some sort. And I haven’t extensively worked with any of the other file types you’ve mentioned, but for xlsx, I highly recommend this package