kamiel79

<p>WordPress has the function wp_localize_scripts for translation, but the strings passed to it have to be hard-coded. Until you parse the .js-files and scan for occurrences of _e() with a fast regexp, and localize them with the data using the WordPress _e-function to localize from a .po file. *Note*. Your po-file has to include strings from javascript files. To do this in Poedit, see http://stackoverflow.com/questions/16557327/how-to-generate-po-file-from-js-file-using-poedit.</p>


Localize js

Provide translation function _e("") in javascript files.

Kasuga

<p>Quick Translate POT/PO/MO Plugin Manual</p>
<h3>1. Introduction</h3>
<p>“Quick Translate POT/PO/MO” is a tool for generating and modifying WordPress plugin translation files.<br />
It allows you to instantly see the effects of your changes and complete the following tasks directly in your browser.</p>
<ul>
<li><strong>Generate POT files (Translation Template)</strong>: Extract translatable strings from a plugin’s source code to create a template file.</li>
<li><strong>Generate and Update PO files (Translation File)</strong>: Create a new PO file for a specific language based on a POT file, or update an existing one.</li>
<li><strong>Edit PO Files</strong>: Directly edit translation strings in an existing PO file.</li>
<li><strong>Generate MO Files (Binary File)</strong>: Automatically create the binary MO file that WordPress uses when you save your PO file edits.</li>
<li><strong>PO File Automatic Translation Tool</strong>: It automatically translates the untranslated parts of a PO file using Google Translation or DeepL.</li>
<li><strong>Download POT, PO, and MO Files</strong>: Download each POT, PO, and MO file to your local directory.</li>
<li><strong>Delete MO Files</strong>: Remove unnecessary MO files.</li>
</ul>
<h3>2. How to Use</h3>
<h3>Step 1: Generating a POT File</h3>
<ol>
<li>Go to the <strong>“1. Generate POT file”</strong> section.</li>
<li>Select the target plugin from the <strong>“Select a Plugin”</strong> dropdown.</li>
<li>Click the <strong>“Generate POT”</strong> button.</li>
<li>If a POT file already exists, a confirmation pop-up will appear.</li>
</ol>
<p>➡ This will create a <code>[text-domain].pot</code> file in the plugin’s <code>languages</code> directory.</p>
<h3>Step 2: Generating and Updating a PO File</h3>
<ol>
<li>Go to the <strong>“2. Generate / Update PO file from POT”</strong> section.</li>
<li>Select the target plugin from the <strong>“Select a Plugin”</strong> dropdown.</li>
<li>Click the <strong>“Generate / Update PO”</strong> button.</li>
</ol>
<p>➡ This will generate a PO file (e.g., <code>ja.po</code>) based on your WordPress language settings.</p>
<p>➡ If the PO file already exists, the existing translations (msgstr) corresponding to the strings (msgid) in the POT file will be preserved in the updated PO file.</p>
<h3>Step 3: Editing a PO File and Generating an MO File</h3>
<ol>
<li>Go to the <strong>“3. Edit PO file & Generate MO file”</strong> section.</li>
<li>Select the target plugin from the <strong>“Select a Plugin”</strong> dropdown.</li>
<li>Click <strong>“Load PO”</strong> to display the PO file contents in a table.</li>
<li>Edit translations directly in the <strong>“msgstr”</strong> column.</li>
<li>Click <strong>“Save Changes and Generate MO”</strong> to save changes and create the MO file.</li>
</ol>
<p>➡ Changes in the editor are saved to the PO file and the MO file is generated simultaneously only when you click the “Save Changes and Generate MO” button.</p>
<h3>For more effective translation work:</h3>
<h3>Step 2.5: Automatically Translate a PO File</h3>
<ol>
<li>Click the <strong>“Go to PO Auto Fill Tool”</strong> button.</li>
<li>Select the target plugin from the <strong>“Select a Plugin”</strong> dropdown.</li>
<li>Choose either <strong>Google API</strong> or <strong>DeepL API</strong>.</li>
<li>Enter the corresponding <strong>API key</strong>.</li>
<li>Click the <strong>“Preview Translation”</strong> button.</li>
<li>Click the <strong>“Save”</strong> button to save the results to the PO file.</li>
<li>Click the <strong>“Back to Quick Translate POT/PO/MO”</strong> button to edit the saved PO file.</li>
</ol>
<p>➡ To use this tool for automatic translation, you need to <strong>register with Google Translation or DeepL and obtain an API key</strong>. Both services can be used within their free usage limits.</p>
<h4>Table Operations</h4>
<ul>
<li><strong>msgid (Source String):</strong> Original string (not editable).</li>
<li><strong>msgstr (Translation):</strong> Editable translation string.</li>
</ul>
<h4>Download A POT File</h4>
<ul>
<li>Click the <strong>“Download POT”</strong> button to download the current POT file.</li>
</ul>
<h4>Download A PO File</h4>
<ul>
<li>Click the <strong>“Download PO”</strong> button to download the current PO file.</li>
</ul>
<h4>Download A MO File</h4>
<ul>
<li>Click the <strong>“Download MO”</strong> button to download the current MO file.</li>
</ul>
<h4>Deleting an MO File</h4>
<ul>
<li>Click the <strong>“Delete MO”</strong> button to remove the current MO file.</li>
</ul>


Quick Translate POT/PO/MO

"Quick Translate POT/PO/MO" is a tool for generating and modifying WordPress plugin translation files.

Localize js vs Quick Translate POT/PO/MO