Laravel 5.4 docs state the following:
For applications with heavy translation requirements, defining every string with a "short key" can become quickly confusing when referencing them in your views. For this reason, Laravel also provides support for defining translation strings using the "default" translation of the string as the key.
So if I use echo __('I love programming.'); and there is no matching translation, it will return 'I love programming.'. So what happens down the line when I decide to add translations? Can Laravel extract all the language phrases I've used and put them into a translation file somewhere? If so, how?
via Chebli Mohamed
Aucun commentaire:
Enregistrer un commentaire