@frank.ringofkeys, sorry, this seems to have fallen through the cracks a few months ago!
We are re-investigating this issue now as a bug and I’ll let you know what we find. Sorry for the delay!
In the meantime (if it’s not too late…) there is a workaround described here: `content_in_locales` field in publish API function - #2 by roger