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
Support multi-byte character sets in config file #72
Comments
Just a small update on this topic. Things are slowly happening. The general roadmap tries to take the slow speed into consideration in order to avoid a feature branch that would need to live for years. It goes like this:
[✔️ = done, 🏃 = in progress, ⌛ = planned] I'll update this comment whenever something fundamental changes. Last update: 2023-12-25 |
- shapes get additional MBCS values - metadata is already converted for real to use bxstr_t*
- shapes get additional MBCS values - metadata is already converted for real to use bxstr_t*
- shapes get additional MBCS values - metadata is already converted for real to use bxstr_t*
- shapes get additional MBCS values - metadata is already converted for real to use bxstr_t*
The feature branch things are happening on is color-unicode. There are already a few test cases with colored unicode box designs, and it's working! We've had some delays because our code base didn't easily allow major refactorings. Currently, I feel we need some more test cases to be confident enough to release something. Also, properly supporting Windows will be an issue, and a lot of required cleanup. But, it's coming along! |
Okay, we released v2.3.0 today with full UTF-8 support in config file! 🎉 Do give it a try! |
We already have Unicode and general multi-byte character set (MBCS) support for input text (from #1), but we'd also like to have that for the config file, so that we can design boxes based on Unicode box drawing characters.
At the moment, the config file is in ASCII format. It should be in UTF-8 format.
The text was updated successfully, but these errors were encountered: