Hi Tony, here you are with a few thoughts on Nikolai's issue. Nikolai is right that <group> and <trans-unit> element have got a lot of common attributes - in fact all possible attributes from <group> are included in the list of attributes for <trans-unit>. In spite of this I'm not sure this would be the best solution to merge those two elements into one as Nikolai suggested . We could just use the elements a little different way. Now I do not have any exact idea and I'm just thinking aloud so anyone feel free to tear it apart. I would add an attribute to the <trans-unit> - similar as Nikolai suggested - called e.g. for-group and we could remove all the attributes from the group element as those are already included in the <trans-unit> element. One <trans-unit> element would contain information for the whole group and the other elements c ould be nested inside the sub group. The structure of the file could look like the following: Example (simplified) ... <group> <trans-unit id= DIALOG1 for-group= yes font= MS Sans Serif;8 style= WS_POPUP WS_CAPTION WS_THICKFRAME coord= 0;0;96;28 > <source/> <target phase-name= after_resizing coord= 0;0;96;28 > -- local version of dialog coordinates </target> </trans-unit> <group> <trans-unit id= IDC_EDIT1 coord= 35;7;53;14 > <source/> <target phase-name= after_resizing coord= 40;7;60;14 > -- local version of editbox coordinates </target> </trans-unit> <trans-unit id= IDCSTATIC coord= 13;9;23;8 > <source>Label:</source> <target phase-name= after_resizing coord= 25;9;35;8 > -- local version of label coordinates Translated Label: </target> </trans-unit> </group> </group> This could solve Nikolai's issue however it could also introduce any new issues I'm not aware of at the moment. I'm looking forward to your response. Cheers, Mirek