-
```
if edipartners are unknown, this leads to 'stuck' situation.
no good error is given, so this is very hard to track.
```
Original issue reported on code.google.com by `hjebb...@gmail.com` on 3 Au…
-
```
use of korean KECA characterset gave error in enveloping.
looks like the handling of this charset works slightly different in python.
```
Original issue reported on code.google.com by `hjebb...@…
-
```
all the optional fields in UNB are now included.
this way these fields can be used in a grammar or user dependent grammar.
```
Original issue reported on code.google.com by `hjebb...@gmail.com` …
-
```
until now bots did not support edifact/x12 grammars with the same record more
than once on the same level.
This is fixed now.
An additional attribute is used in get() and put(), eg:
get({'BOTSID'…
-
```
When receiving many edi-messages, receiving 'wrong' edi-message is unavoidable
(when receiving 100.000edi-files per month, with 0.1% errors, this is 3 errors
per day).
You want to be able to rep…
-
```
newer versions of x12/edifact have repeating composites and data elements
```
Original issue reported on code.google.com by `hjebb...@gmail.com` on 8 Apr 2013 at 12:35
-
```
newer versions of x12/edifact have repeating composites and data elements
```
Original issue reported on code.google.com by `hjebb...@gmail.com` on 8 Apr 2013 at 12:35
-
```
the bots mapping script typically handles one 'message'.
I want an option to access and fill all envelope fields from the mapping.
for incoming:
inn.envelope: a dict with all fields from envelope…
-
```
edifact and x12 is often received as one big string (no cr/lf).
when displaying this bots now formats these files to one segment per line.
```
Original issue reported on code.google.com by `hjeb…
-
```
Raw editype:
nothing is done:
it is just read and passed to translation (incoming)
or written to file (outgoing).
Use case:
- making eg pdf file in translation, just write it.
- passing text fil…