Hi Howard,
The rule is: you leave everything where it is for backwards compatibility of the language packs and introduce new files/strings/places, if necessary with an index (say the content of aiken.html changes a lot, so that becomes aiken2.html).
At the San Francisco Moot I raised the following issue to Martin: since Moodle 2.0 breaks e.g. the php 4 compatibility and can be a really new start for a lot of things, why not break the backwards compatibility of the language packs too, do a search of all not used string, help files etc. and make the packs smaller for translators from new languages who start translating from 2.0 onwards (see MDL-15252).
Languages
Moving stuff - advice
This discussion has been locked so you can no longer reply to it.