PROBLEM:

When a BCONF is edited wrongly in RAINBOW and the source-srx is called e.g."languages-source.srx" and the target-srx is called e.g. "languages-target.srx" BUT in the pipeline both are encoded as "languages.srx" (can happen very easily with rainbow as this is the default !!) then our BCONF-Import will use the 2nd encoded SRX as the only one used for source and target "languages.srx". 

SOLUTION:

This behaviour opposes the Longhorn behaviour where the Pipeline-settings seem to be ignored. Therefore the translate5 BCONF import should mimic the Longhorn behaviour where the encoded SRX and their names have the lead over the SRX (names) encoded in the Pipeline.