Skip to content

documenting use of nested directory structure for translation files #3957

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

documenting use of nested directory structure for translation files #3957

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions localization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,16 @@ Of course if you are using the [Blade templating engine](/docs/{{version}}/blade

If the specified translation string does not exist, the `__` function will simply return the translation string key. So, using the example above, the `__` function would return `messages.welcome` if the translation string does not exist.

If you are using a nested directory structure, you should specify the path to the translation file using forward slashes:

{{ __('invoices/customer.title') }}
{{ __('invoices/business.title') }}

// and not:

// {{ __('invoices.customer.title') }}
// {{ __('invoices.business.title') }}

<a name="replacing-parameters-in-translation-strings"></a>
### Replacing Parameters In Translation Strings

Expand Down