Parse `<source>` properly with its asterisks

Especially the order="2" entries where the asterisks are used as delimiters.

```


















```

Start by locating the Ruby entry point that parses elements and reproduce the issue with the supplied order="2" examples. Check how asterisks in the details attribute are split or retained. Done means these entries parse without losing their asterisk-delimited fields, including the repeated empty fields.

Written by the indexing model from the issue text.