github-actions[bot]
commented
3 hours ago :sparkles: Thanks for sharing your idea! :sparkles:
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).
The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+
Don’t forget to upvote the top comment with 👍!
Verified feature request does not already exist?
đź’»
Pitch: what problem are you trying to solve?
In Japan, it is still common for CSV files to be encoded in Shift-JIS rather than UTF-8 and this makes it annoying for my workflow where I have to download the file, open it up with some software to convert it to UTF-8.
I am not sure if any other region has this issue where UTF-8 is not the default encoding for CSV files.
Describe your ideal solution to this problem
The CSV import modal already provides many options for customizability. Maybe file encoding can be an addition?
Teaching and learning
No response