eprbell

I also just finished the new localization infrastructure for generated reports: now it's possible to generate Japanese taxes both in Japanese or in English (or in any other ISO 639-1...

I recently added a bunch of RP2 issues requesting help in adding support for various countries: here follows the blurb I wrote for these issues (it's useful because it contains...

This issue is in progress: @macanudo527 already added the country plugin for Japan (bullet 1 in the list above).

I think it may be easier than it seems. We could just let the accounting engine do its thing, say with FIFO (default for Japan). Then in the Japan-specific output...

BTW, not sure how fluent you are in Japanese, but if you like you can localize the Japanese report so that it outputs in English and in Japanese (and in...

Yes, it's correct that these sets will contain the result of all data processing, including transaction resolution, price pair conversion, time filtering (via `-f` and `-t` CLI options in RP2),...

They are: `intra_transaction_set` is a property of `computed_data`. I mentioned it because in your earlier message you listed only `in_transaction_set` and `out_transaction_set`. See an example of use at: https://github.com/eprbell/rp2/blob/main/src/rp2/plugin/report/rp2_full_report.py#L661

Right: the artificial fee-only transactions added by ods_parser.py should appear in the `out_transaction_set` of `computed_data`. Feel free to improve the docs: let's add a FAQ or something to make it...

I finally managed to commit the changes needed to distinguish default output plugins from non-default ones (default ones are specified [here](https://github.com/eprbell/rp2/blob/main/src/rp2/configuration.py#L31)). The user can now define an optional `generators` section...

Here's another idea. Maybe let's get rid of all the existing Crypto and USD fields and try with: * Crypto In, Crypto Out, Crypto Fee * USD In, USD Out,...