Thinking about a better internationalisation system

Hi guys!

First, I have to say thanks for the work you all have done to build this library. It's always great to have a decent Faker library in any programming language.
I was thinking about the way this library handles i18n. I'm a bit afraid that if we continue to contribute on several languages, using a language namespace will make the documentation enormous.

To be honest, I don't have a solution of my own except reproducing the method that works elsewhere like using YAML file as Faker's Ruby did. Also, I searched about gettext because this is the i18n library by default of Phoenix but I'm not sure that's the right solution here. I just wanted to start the conversation about this with you guys. 😄

The issue does not name any files, tests, or implementation entry points. Start by locating the library's current internationalisation and language-namespace implementation, then compare the trade-offs of YAML-based translations and gettext for Elixir/Phoenix. Done would require an agreed design and documented migration or implementation scope.

Written by the indexing model from the issue text.