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.

Konstantin Obenland

<p>This plugin replaces the author slug with a sanitized version of the user’s display name.</p>
<p>This plugin will not prevent hackers from finding out your login name but the login name won’t be visible<br />
in the author archive’s URL, which works towards your friendly URLs with using your display name.</p>
<p>DO NOT use this on a site with more than 1000 registered users, as updating all of their nicenames at once might break your site.</p>


WP Author Slug

Easy way to add some obscurity to login guessing.

But please update as it's over 2 years now.

Excellent

This plugin would probably work OK if you have a small number of users (e.g. if your site doesn't allow public login). But if you have a large number of users (e.g. if you are running ecommerce or allow users to register for other reasons), this plugin will probably take down your site.

The reason is that there are hooks that run when you activate or delete the plugin. It runs database fetch and update queries on every user in your database, all in-line on the request (rather than background via a cron). So if you have a thousand or more users it attempts to do a thousand or more database writes when you click Activate or Delete from the plugins list. This will likely grind your website to a halt. 

It would be better/useable if you could either choose to only apply these scripts to specific user types (e.g. Author) or if you could run the update in batches in the background.

Don't use if you have a large user database

Add a layer of security and prevent your login name from being shown in the author archive's URL.

SLUG TRANSLATER vs WP Author Slug