Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CSV import rules, encoding #1777

Open
PSLLSP opened this issue Dec 8, 2021 · 1 comment · May be fixed by #2319
Open

CSV import rules, encoding #1777

PSLLSP opened this issue Dec 8, 2021 · 1 comment · May be fixed by #2319
Labels
A-WISH Some kind of improvement request, hare-brained proposal, or plea.

Comments

@PSLLSP
Copy link

PSLLSP commented Dec 8, 2021 •
edited
Loading

Is it difficult to add new option for CSV import rules, option to define encoding of CSV file? I assume that hledger works with UTF-8 encoding by default. I have some CSV files in encoding CP1250 (Windows-1250), so I have to convert them before import with recode cp1250..u8 FILE.csv.
@PSLLSP PSLLSP added the A-WISH Some kind of improvement request, hare-brained proposal, or plea. label Dec 8, 2021
@simonmichael
Copy link
Owner

Probably not so difficult at least at first, I would consider a PR especially if it includes an impact and cost assessment or if someone is keen to champion this. Otherwise I recommend that people preprocess data as you have done, just to limit our scope and maintenance/support costs. We could also document that as a first step.

@jokesper jokesper linked a pull request Jan 21, 2025 that will close this issue
Draft
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-WISH Some kind of improvement request, hare-brained proposal, or plea.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement encoding in .rules jokesper/hledger
2 participants
@simonmichael @PSLLSP