Hello,
before all else, thank you very much for this module!

I have successfully created an importer as described in the documentation for importing XML data into a Drupal node type.

I was quite happy until I saw that my target node infrastructure actually contains unnecessary redundancies: I have a language definition field in it whose data could actually be imported as an attribute (= table field entry in the database) of the field whose language it is actually defining - IF I could figure out how to do this!

However, when I go to define mappings, it seems I can only define targets via the dropdown of available fields. To achieve what I need, I would need to target not my_cute_datafield, which can be found in that list, but rather my_cute_datafield.language.
I cannot workaround by (mis)using the node language (which is available as the option "language" in the dropdown) because I am already using that for the node. The problem is that while the content of my_cute_datafield usually is in the same language as the node itself, it can also differ from it, and thus needs specific defining.

Hence my question:
Is there any way I can build my query to have the language of my_cute_datafield mapped directly into the "language" table field that is already included by default in every data_field table?

Thank you for any help on this!