Damian M. G.

Haha awesome. I do follow your project on github already, in fact, we exchanged some words on past years, I had another pseudonym (IgorJorobus), we fixed a few things. Thanks for the good vibes, have a good day! D.

Hello Matthieu, I've given you credit and thanks for your library, which was used for my project xlsx_drone. Be free to check it out: https://github.com/damian-m-g/xlsx_drone I'll increase the use of sxmlc when I provide writting functionality to xlsx. Cheers & thanks, D.

Happy New Year! :)

Hi Matthieu, Thanks for the quick answer. I was dealing with this issue since 2 days ago, it happened to be a bug in my C code that caused the segfault. As cross-language debugging isn't possible, I wasn't able to debug the C code where things failed. So today I started dropping some printf() to track the problem and found out a bug in my code. After fixing that, everything works good. I'm able to use all my functions, and to instruct Ruby to take those strings as UTF-8. So I would say, for anyone...

Hello Matthieu, I'm working with utf-8 xml files without bom without using the SXMLC_UNICODE features and everything seems to work great, my test assertions with utf-8 strings works okay. Even that, I'm having issues when calling a C function that sets utf-8 strings with a FFI, binding to Ruby. When I call it to set ASCII strings works great, but when UTF-8 is involved, the call to that function triggers a Segfault error. My question is: do I must include support for unicode (-DSXMLC_UNICODE) even...