Contributing

Contributions are welcome and will be fully credited.

We accept contributions via Pull Requests on GitHub:

• Laravel Lang: Common
• Laravel Lang: Publisher
• Laravel Lang: Lang
• Laravel Lang: Attributes
• Laravel Lang: HTTP Statuses

How can I add localization?

• Fork the desired repository (Lang, Attributes or HTTP Statuses);
• Make sure you have PHP 8.1 or higher installed on your computer;
• Install dependencies by running console command:

  composer update
  

• Call the console command, passing in the argument the name of the localization to be added. Localization code must comply with ISO-15897 and ISO-639-1 (ex: fr for French):

  vendor/bin/lang create fr
  

• This command will create all the necessary files and fill them with initial data. The files will be located in the locales/{locale} directory;
• Keep in mind that the *-inline.json files does not come with Laravel and the idea of this file is not to put a specific name to each attribute (as in validation.php) but a generic name for the validation attributes. Therefore in the translations of this file the placeholder :attribute should not appear.
• Add a pull request with the name of the language. For example:

  [fr]: Added new localization

How can I fix the file?

• Fork the desired repository (Lang, Attributes or HTTP Statuses);
• Update the files;

  Note that in inline files (json-inline.json and php-inline.json), keys are the "non-inline" option.

  For example:

  {
    "The :attribute must be at least :length characters.": "This field must be at least :length characters."
  }
  

• Add a pull request with the name of the language

  ex: [fr]: Updated translations

What is the difference between "inline" files and "non-inline" files?

• php.json - contains translations of values for PHP localization files.
• php-inline.json - contains inline translations of values for PHP localization files.
• json.json - contains translations of values for JSON localization files.
• json-inline.json - contains inline translations of values for JSON localization files.

At the same time, the Laravel Framework itself also contains JSON keys:

• laravel/framework#9.x/src/Illuminate/Auth/Notifications/VerifyEmail.php#L65-L68
• Laravel-Lang/lang#main/source/framework/9.x/framework.json

At the same time, the project structure is not tied to specific packages or files. For example, the Laravel-Lang/http-statuses project contains translations of statuses, while Laravel-Lang/attributes contains attributes for validation files.

Using the template, you can create any project with any translation keys.

This file structure allows you to support translation for several product versions at once. For example, Jetstream 1.x, 2.x, 3.x and dev versions.

What should I do if there is a tag whose translation is the same as in English?

In some languages there are some strings whose translation is the same as in English. In this case, the script that generates the status adds them by default to the list of pending translations. This affects the completion status for this language which would never be marked in status list with ( ✔) but with (❗) even if all other strings were translated.

We can avoid this situation in the following way:

• Fork this repository if you haven't already;

• Create a _excludes.json file in the localization folder if it doesn't already exist;

• This file contains an array of values for each exception.

  For example, we need to exclude Micronesia from the status check for Italian:

  locales/it/json.json:

  {
      "Micronesia, Federated States Of": "Micronesia"
  }
  

  locales/it/_excludes.json:

  [
      "Micronesia"
  ]
  

• Add these changes to the pull request you will send.