You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading files with sequences using Undefined Length, which contain items also using Undefined Length, the Sequence Item Delimiter (FFFE,E00D) is being parsed as an element.
The standard provides an example of a similar scenario:
In my case, all my items are of undefined length.
I'm using v1.8.20.
The text was updated successfully, but these errors were encountered:
@Gaelik-git In a way, yes, but I'd like to keep it since it deals with the item delimiter, not the sequence delimiter. This is going to be a tricky one because the standard considers the sequence delimitation item as part of the sequence element's value, but does not consider the item delimitation as part of the item's value. This is shown in the image above.
@rennerg Any thoughts or preferences on what you'd like to see here?
When reading files with sequences using Undefined Length, which contain items also using Undefined Length, the Sequence Item Delimiter (FFFE,E00D) is being parsed as an element.
The standard provides an example of a similar scenario:
In my case, all my items are of undefined length.
I'm using v1.8.20.
The text was updated successfully, but these errors were encountered: