Let's have CLD on Laravale.
1) Can be done as it is native to Lara is done with the files with field values, separating the directories en EN es, etc.
2) Or can be connected gettext
, which is already a standard, used everywhere, Yes even here on the toaster tag there is.
3) maybe there is some TRU option?
- MULTILANG in the database - non-kosher)
The question arises: what are the pros and cons first?
the first kind native out of the box, so in theory should be fast. But gettext - a professional tool for localization, where everyone is provided for, and the l2r and the plural, and birth and case and all that.
The idea is that the extra plugin with his file can affect performance. But there is compiled .mo
So all the same, even if scanty, but the performance will differ?
The second bonus that I see gettext this Poster and/or online translation tools. For yourself or for a community, if someone wants to interpret.
On the other hand, if the project only 2 or 3 languages, you can translate the native files of Lara, and more not to touch them.
What are the pros and cons, to consider the use or non-use of gettext in laravale?