Fix *.md linting errors
This commit is contained in:
parent
715b4ccc31
commit
ab281ac1d2
|
@ -32,18 +32,18 @@ If you’re new to translating, check out the [translators handbook](https://mak
|
|||
|
||||
### Downloading translations from translate.wordpress.org manually
|
||||
|
||||
1. Go to https://translate.wordpress.org/projects/wp-plugins/woocommerce and look for your language in the list.
|
||||
1. Go to [translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/woocommerce) and look for your language in the list.
|
||||
2. Click the title to be taken to the section for that language.
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/2016-02-17-at-09.57.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/2016-02-17-at-09.57.png)
|
||||
|
||||
3. Click the heading under `Set/Sub Project` to view and download a Stable version.
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/2016-02-17-at-09.59.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/2016-02-17-at-09.59.png)
|
||||
|
||||
4. Scroll to the bottom for export options. Export a `.mo` file for use on your site.
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/2016-02-17-at-10.00.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/2016-02-17-at-10.00.png)
|
||||
|
||||
5. Rename this file to `woocommerce-YOURLANG.mo` (e.g., Great Britain English should be `en_GB`).
|
||||
6. Upload to your site under `wp-content/languages/woocommerce/`. Once uploaded, this translation file may be used.
|
||||
|
@ -58,23 +58,23 @@ WooCommerce includes a language file (`.pot` file) that contains all of the Engl
|
|||
2. Go to the new Loco Translate menu item created in your Dashboard with five sub-sections.
|
||||
3. Go to the `Plugins` section, and select `WooCommerce`.
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-woocommerce.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-woocommerce.png)
|
||||
|
||||
4. Add new languages using the `Add New Language` link.
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-new-language.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-new-language.png)
|
||||
|
||||
5. Choose the language to add in the list, or enter the language ISO code (ex: `fr_FR`, `en_US` etc.), select the folder to add the translation files to, and click `Start Translating`.
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-create-language.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-create-language.png)
|
||||
|
||||
> **Note:**
|
||||
>
|
||||
> - Loco Translate offers three different locations for where to create the translation. The best choice for your own translation is Custom, not just to prevent custom translations from being undone by updates, but also because it’s needed for strings in extensions like WooCommerce Subscriptions to be properly translated. Avoid the Author location since it’s inside the plugin and will be overwritten by extension updates, as well as the System location, which could be overwritten by translations from translate.wordpress.org.
|
||||
> - If you encounter any technical issues while using Loco Translate, please get in touch with the Loco Translate support team: https://wordpress.org/support/plugin/loco-translate/
|
||||
> - If you encounter any technical issues while using Loco Translate, please get in touch with [the Loco Translate support team](https://wordpress.org/support/plugin/loco-translate/).
|
||||
|
||||
6. Save when finished.<br>
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-translating-1.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/loco-translate-translating-1.png)
|
||||
> **Note:** When a new version of WooCommerce is released and updated on your site, you need refresh the .po file to look for new strings. Use the “Sync” button to find any new string to start translating.
|
||||
|
||||
## Creating custom translations with PoEdit
|
||||
|
@ -86,11 +86,15 @@ WooCommerce comes with a `.pot` file that can be imported into PoEdit to transla
|
|||
To get started:
|
||||
|
||||
1. Open PoEdit and select `Create new translation from POT template`.
|
||||
2. Choose `woocommerce.pot` and PoEdit will show the catalog properties window.<br>
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/Screen-Shot-2013-05-09-at-10.16.46.png)
|
||||
2. Choose `woocommerce.pot` and PoEdit will show the catalog properties window.
|
||||
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/Screen-Shot-2013-05-09-at-10.16.46.png)
|
||||
|
||||
3. Enter your name and details, so other translators know who you are, and click `OK`.
|
||||
4. Save your `.po` file. Name it based on what you are translating to, i.e., a GB translation is saved as `woocommerce-en_GB.po`. Now the strings are listed.<br>
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/Screen-Shot-2013-05-09-at-10.20.58.png)
|
||||
4. Save your `.po` file. Name it based on what you are translating to, i.e., a GB translation is saved as `woocommerce-en_GB.po`. Now the strings are listed.
|
||||
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/Screen-Shot-2013-05-09-at-10.20.58.png)
|
||||
|
||||
5. Save after translating strings. The `.mo` file is generated automatically.
|
||||
6. Update your `.po` file by opening it and then go to `Catalog » Update from POT file`.
|
||||
7. Choose the file and it will be updated accordingly.
|
||||
|
@ -135,7 +139,7 @@ Upon activation, the plugin prompts you to specify:
|
|||
|
||||
You may see that some of the strings are not being translated on the Checkout page. For example, in the screenshot below, `Local pickup` shipping method, `Cash on delivery` payment method and a message related to Privacy Policy are not being translated to Russian while the rest of the form is indeed translated:
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2012/01/not_translated.jpg)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2012/01/not_translated.jpg)
|
||||
|
||||
This usually happens when you first install WooCommerce and select default site language (English) and later change the site language to another one. In WooCommerce, the strings that have not been translated in the screenshot, are stored in the database after the initial WooCommerce installation. Therefore, if the site language is changed to another one, there is no way for WooCommerce to detect a translatable string since these are database entries.
|
||||
|
||||
|
@ -172,4 +176,4 @@ If some of your translated strings don’t show up as expected on your WooCommer
|
|||
|
||||
If this is the case, then it is necessary to translate both these forms for your translation to work as expected. To do this, please use the Single and Plural tabs that show up in the translation section:
|
||||
|
||||
![](https://woocommerce.com/wp-content/uploads/2023/03/Single_Plural_Loco_Translate-1.png)
|
||||
![screenshot](https://woocommerce.com/wp-content/uploads/2023/03/Single_Plural_Loco_Translate-1.png)
|
||||
|
|
Loading…
Reference in New Issue