Sometimes the order of translation entries matters. And an alphabetic sort does not really work well as it ruins logical groups. Let's just assume that I cannot control the name of the identifiers.
Now an additional column that is changeable that gives the index of the entry plus an option to sort by that index would be great.
Next an option to write back elements using that index number would be great too. Or better, in general, a button to write back elements using the current ordering of that grid. The index number itself should not be stored, it's just a temporary field, discarded on closing. There should be only one index using the main resource file, sub locales use the same ordering as the main. I think that makes sense in all cases.
And finally, to allow manual adjustment between entries, if that index number in the column would allow for gaps, meaning the value written in the column is Index * 100 + 0, it is easily possible to change the ordering value of other entries. It allows for 2 digits to adjust. Then I can finally resort without having to manually open and change all .resx files.
Now an additional column that is changeable that gives the index of the entry plus an option to sort by that index would be great.
Next an option to write back elements using that index number would be great too. Or better, in general, a button to write back elements using the current ordering of that grid. The index number itself should not be stored, it's just a temporary field, discarded on closing. There should be only one index using the main resource file, sub locales use the same ordering as the main. I think that makes sense in all cases.
And finally, to allow manual adjustment between entries, if that index number in the column would allow for gaps, meaning the value written in the column is Index * 100 + 0, it is easily possible to change the ordering value of other entries. It allows for 2 digits to adjust. Then I can finally resort without having to manually open and change all .resx files.