It is highly unlikely I will implement this.

There are reasons why Composr normally would not allow full stops. There could be confusions with file extensions. It could confuse URLs / permalinks as well. And there are several ways this could end up getting abused on the security front (such as creating pages with a double full stop to try a directory traversal attack).

Patrick is correct. Codenames are intentionally limited to not contain anything that is likely to be syntax in some other 'language'.
Comcode pages can have monikers, so arbitrary URLs can be achieved. For actual filenames, dashes could be used (for example) rather than dots.

Fair enough. I don't plan to use monikers, meta tags or anything else that is available via edit on these pages I just found it strange I couldn't edit them via Composr due to the . being present. They are inlet/landing pages and I wanted to include the country 2 letter ISO code in case bands share the same name. numento-fi.txt would work if I wanted to edit them but I think I will just hand edit these pages as they do seem to work fine. Thanks :)