When supplied with an unknown root key, we expect to create a new i18n file instead of raising an exception.

Should it do both? Otherwise in case of a typo you'd suddenly have a completely new language to delete. So an exception unless run with -c (for create), for example.

It does not create a new language. It creates a new translation file alongside conf.php, sub.php, etc for all languages.

If there is a typo, I think it's easy to revert with a simple command like find app/i18n -iname \*xxx.php* -delete if we've created xxx.php files.

If you try to update a key with an unknown root key, you still have the exception.

If there is a typo, I think it's easy to revert with a simple command like find app/i18n -iname *xxx.php* -delete if we've created xxx.php files.

I don't mean from that perspective, but from the perspective of not noticing for 10 minutes and suddenly needing to try to merge conf.php and comf.php

If there is a typo, I think it's easy to revert with a simple command like find app/i18n -iname xxx.php -delete if we've created xxx.php files.

I don't mean from that perspective, but from the perspective of not noticing for 10 minutes and suddenly needing to try to merge conf.php and comf.php

I see what you mean. I'll figure something else.

@Frenzie I've change the whole thing to introduce an add-file feature. This way, there is no side-effect on other section of the code.

Sounds good to me. 👍