Rafał Miłecki

Confirmed in https://github.com/invoice-x/invoice2data/issues/381 that `-m` works.

I guess you expect something like ``` [ { "position": 1, "qty": 5, "unit_price": 5.0, "total_price": 25.0, "order_number": "AB-12345" }, { "position": 2, "qty": 1, "unit_price": 10.0, "total_price": 10.0, "order_number":...

What I believe is be the best option for you is to 1. Write a small Python script 2. Use `invoice2data` as library 3. Extract data and process it in...

Support for multiple (different) `line` patterns was added in the https://github.com/invoice-x/invoice2data/pull/417 - that should help.

Implemented in the f59d6838db62dd6c322f99cf274e7f5687adb00d ("input: add support for plain text")

@kavinsharma: I think implementing this feature as separated plugin is non optimal and will cause maintenance problems in a long term. You add another piece of code handling regular expressions....

Looks good except for a bit messy commits. We have some (unneeded?) merge commit and commit adding `extract_data()` call. If all those changes can be squashed into single commit during...

I'm all for documenting some standard field names! I tried starting discussion on field name for VAT summary lines in the #309 but it was somehow missed. I noticed e.g....

Following some existing standard would be great. Is there anything more international than Zugferd? Let me post a merge request which what I already got queued while working on the...

Thanks @m3nu! It seems there is UE directive 2014/55/UE also called "eInvoicing Directive". Resources on eInvoicing: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eInvoicing . It indeed specifies CCI and UBL as supported syntaxes: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Required+syntaxes I think...