Isamu Takeda

<ul>
<li>At the moment, it has a function to translate Japanese into English and replace the sanitized one.</li>
<li>The default setting is to replace it when the post is saved.</li>
<li>If you want to replace saved posts, you can set it on the setting screen.</li>
<li>
<p>Categories, terms, and tags can also be replaced.</p>
</li>
<li>
<p>English translation function</p>
<ul>
<li>This plugin uses the API of “Minna no Jido Honyaku”.</li>
<li>Please register as a user of <a href="https://mt-auto-minhon-mlt.ucri.jgn-x.jp/" rel="nofollow ugc">Minna no Jido Honyaku</a> in advance and obtain the authentication information.</li>
<li>You can register the authentication information from the setting screen.</li>
<li>This plugin uses the API of “Google Cloud Translation API”.</li>
<li>Get the project ID and API key obtained by creating a project and enabling the Cloud Translation API from the <a href="https://console.cloud.google.com/home/dashboard" rel="nofollow ugc">Google Cloud Platform dashboard</a>.</li>
<li>You can register the authentication information from the setting screen.</li>
</ul>
</li>
</ul>
<h3>Related Links</h3>
<ul>
<li><a href="https://github.com/itmaroon/slug_translater" rel="nofollow ugc">Github</a></li>
</ul>
<h3>Arbitrary section 1</h3>


SLUG TRANSLATER

Translate the slug generated in Japanese into English and replace it with an appropriate format.

Milan Dinić

<p>Change Core Slugs is a plugin that allows you to set custom permalink slugs instead of default ones that are provided with WordPress core. This functionality is already available in WordPress, however it can be used by manually setting new configuration in the code. What this plugin does is that it provides friendly user interface where all site admins can change default slugs.</p>
<p>You can change:</p>
<ul>
<li><code>author</code> base in authors archives</li>
<li><code>search</code> base in searches archives</li>
<li><code>page</code> base in pagination pages of archives or in single posts</li>
<li><code>comments-page</code> base in pagination pages of single posts comments</li>
<li><code>comments</code> base in comments feeds</li>
<li><code>feed</code> base in feeds</li>
</ul>
<p>When you change any slug, you will not get redirection from the pages that used old slug. Same goes if you again change any slug. If you want redirection, you must set it through server rules or with other plugins.</p>
<p>If you disable this plugin, old, default slugs will be restored and URLs with new slugs will stop working. The only way to keep new slugs is by manually setting them in the code.</p>
<p><strong>NOTE</strong>: because of two bugs in WordPress core, in some cases setting custom slugs will not work properly. These cases are when <code>page</code> or <code>comments-page</code> include any non-ASCII character (ticket <a href="https://core.trac.wordpress.org/ticket/41891" rel="nofollow ugc">#41891</a>), or when <code>feed</code> or <code>comments</code> bases are set (ticket <a href="https://core.trac.wordpress.org/ticket/43274" rel="nofollow ugc">#43274</a>). Until these two bugs are fixed, you can use <a href="https://github.com/dimadin/redirect-canonical-fix" rel="nofollow ugc">temporary plugin</a> that includes fixes. You do not need that plugin if you do not use features that trigger bugs from above.</p>
<p>And it’s on <a href="https://github.com/dimadin/change-core-slugs" rel="nofollow ugc">GitHub</a>.</p>
<h3>Usage</h3>
<p>Got to Settings > Change Core Slugs page.</p>


Change Core Slugs

Set custom permalink slugs instead of default ones.

SLUG TRANSLATER vs Change Core Slugs