![poedit accept fuzzy translation poedit accept fuzzy translation](https://mbrsolution.com/wp-content/uploads/2012/10/suffusion-make-changes.png)
This is not recommended so by default you will be warned. If a POT file is missing Loco Translate can sync directly to the source code. Sync with source when template missing (default: warn) Switching this option to 0 (zero) disables fuzzy matching completely. The higher the value the more likely a string will be kept.
#Poedit accept fuzzy translation how to
This option specifies how to treat redundant strings when a sync operation drops them from existing PO files. If you have problems uploading files to your server then try disabling this option. It's recommended to enable file uploads because long form fields can cause problems with some security software. When disabled, the file source is sent as if it were a form field. When enabled the source is sent as a concrete file upload. This changes how the file editor posts PO files to your server.
![poedit accept fuzzy translation poedit accept fuzzy translation](https://eventespresso.com/wp-content/uploads/2012/12/poedit.png)
We don't recommended you enable this option, unless you need it for compatibility with other editing software.
![poedit accept fuzzy translation poedit accept fuzzy translation](https://d33v4339jhl8k0.cloudfront.net/docs/assets/55192029e4b0221aadf23f55/images/59a923b52c7d3a73488c8804/file-gJ4d1CW7kb.png)
This option causes Loco Translate to prepend a 3 byte UTF-8 BOM to all newly written PO and POT files. Set this value to 0 (zero) to disable line wrapping completely. This number controls the line wrapping (or page width) of all newly written PO and POT files. The format for a backup file name is -backup-.~ Switching this to 0 disables backups completely.Ĭurrently you can only restore backups manually by accessing the file system over FTP or SSH. The default is 1, meaning every save action creates a new backup and deletes any older backups. This option specifies the number of previous revisions to keep when a PO or POT file is updated. Number of backups to keep of each file (default: 1) The rules are exactly the same as for PHP: JavaScript files must use standard WordPress l10n functions and specify text domains. Add extensions such as "js" to enable this. Scan JavaScript files with extensions (default: none)Įxperimental feature: Loco Translate 2.2.0 added support for JavaScript string extraction. Loco Translate 2.0.16 added support for Twig templates, but note that only the PHP syntax used by Timber is currently supported. When extracting strings from PHP source code, Loco Translate will look only in files with these extensions. Scan PHP files with extensions (default: php twig) "50K" for kilobytes, "1M" for megabytes or "2048" for an exact number of bytes. This option takes a value in PHP shorthand style, e.g. Try lowering this value if you hit a memory limit, but raise it if files containing required strings are skipped. Files larger than this limit will not be scanned for strings. Setting the maximum size of a PHP file can avoid memory usage problems. Skip PHP files larger than (default 100K) These options are observed when extracting translatable strings to generate templates. Settings are saved as WordPress site options, so they take effect per site where the plugin is available. The following options are available across the plugin's usage by every user that has access. Optional settings for the Loco Translate plugin