Blog Management

I tried to expand my blog in English on Polylang.

小林 祐也(ゆーや@ブログ運営者)

In order to solve daily problems, we are planning a mechanism to disseminate life hacks and health care know-how, and to spread the teal organization and value principle that will lead the next era.

I want to easily expand my blog in multiple languages and increase the reach target from 130 million japanese-speaking people to 1.5 billion english-speaking countries! Have you ever thought so?

I had thought so several times, but it seems to be quite difficult, so I had not implemented it, but this time I tried using a plug-in called Polylang to english a part of the blog. This time, we will introduce the unknown points, points to note, and impressions that I implemented in the setting method of this plug-in.

Recommended for such a person

  • If you are an Affinger blogger who is considering multilingualization
  • If you're not sure how to set up Polylang

Why choose Polylang?

First of all, I will explain the background of choosing Polylang, but what kind of plug-ins can translate multiple languages are divided into pre-translation type and real-time translation type.

The latter real-time translation type plug-in has also included this blog, but since the translation function has been provided in the browser, isn't it necessary to use such a plug-in in the first place? So I deleted it.

This time, I was looking for a pre-translated plug-in, but among them, there were two plug-ins that were free to use as candidates and reputable plug-ins such as "Bono" and "Polylang". When I actually tried Bono, page purification was able to generate An English page without breaking the structure of the blog, but the contents had to be translated and written by myself, and Bono quit because I thought it was hard to translate everything from 1.

Polylang, on the other hand, is a machine translation, but it automatically generates the article after translation. This was the deciding factor and I decided to use Polylang.

How to install Polylang and Lingotek Translation

In order to expand multiple languages using Polylang, it is necessary to introduce a plug-in called "Lingotek Translation" separately. As for how to install here, there are many ways to do it when you search on Google, so here we introduce a helpful page and will not care.

English translation of blogs using Polylang and Lingotek Translation

We will introduce the setting for english translation of blogs using Polylang and Lingotek Translation, and in order that it is better to implement it as a procedure for English translation.

1. English translation of menu

The title, header, and footer menus change from customizing the appearance.

Since the English menu application field is increasing with checkboxes, create and assign a new menu with an English name

This way, the menu will be written in English when you open the English page.

The menu is in English!

I think that there are many people who menu fixed pages, so don't forget to create english-translated content for the fixed page itself.

2. English translation of profile

An English profile field has been added to the user list, so let's enter an English translation there.

If you don't enter this, your profile will be empty when you open the English translation.

3. English translation of "The Person Who Wrote This Article"

The characters for the person who wrote this article cannot be modified unless you directly change the theme editor. The following is written in japanese in the contents of "st-author.php" ...

Let's translate it into English separately in the language locale as follows.

Example English translation

The result of the English translation

4. English translation of widgets

The widget has added a box to select a language as follows, so I added one for Japanese and One for English.

Results of implementation

Implementation result of the widget under the smartphone article: The left is an English translation version and the right is the Japanese version

5. English translation of categories

The categories are lingotek translation of the integration plug-in, and it was automatically generated by updating the categories one by one with the category column automatic.

The caveat at this time is to do so from the parent category. This is because if you do not create an English translation from the parent category, the hierarchical structure will not be created correctly.

6. English translation of tags

The tags were organized from the original tags, and the lingotek Translation profile above was "Atomatic" and then translated in bulk.

If your tags are cluttered with categories, we recommend that you organize them at this time.

7. English translation of the article

We recommend that you complete all of the above before translating the article into English. Otherwise, you will have to re-set the categories and tags, and you will release the article in a halfway state.

7.1.Polylang Settings

Here are some recommendations for translating articles into English:

I will explain the points to be set in detail one by one and why.

7.1.1.URL Correction

UrLs should be set from directory names in pretty permalinks, unless you are thinking of separating subdomains by language.

On the right, "Do not display language information in the default language in the URL" is recommended for checking. This is because the URL of the Japanese article will change if you uncheck it, and you will not be able to access it from the linked site so far.

7.1.2. Browser language detection

Browser language detection is recommended. This is a feature that displays an English page when accessed in English, and it is easier to enable it for users who have accessed from English-speaking countries, so let's enable it.

7.1.3.Media

Media is recommended for invalidation. If you enable media, the gallery added to the article will not be able to be viewed in english version, and reupload correspondence is required.

7.1.4.Sync

It is recommended that synchronization be set as follows:

Noteworthy points are custom fields. If you check custom fields, you will not be able to write meta descriptions separately in English and Japanese, so it is recommended to uncheck them.

7.2.Lingotek Translation Settings

7,2.1.Manage

In lingotek Translation's Manager settings, we recommend Manual in the Post and Fixed Page Profiles for settings related to the English translation of articles.

If you make this automatic, english translation articles will be generated at unintended timing.

7,2.2.Settings

In Settings, it is important to set download translation status on the Premiums tab, and drafts are recommended. If you set this to "Published", the article will be renewed before proofreading the English translation article.

The English translation article will be described later, but since there are always corrections, it is better not to publish it as it is.

7.3. How to translate the article into English

When translating articles into English, it is recommended to implement them in bulk operations in the list in order to implement them efficiently.

7.3.1.Filtering

In Polylang and Lingotek Translation, the featured image disappears when you run the English translation. It is better to reset this as soon as possible, so narrow it down by user, category, date, and translate as much as you can within the day.

7.3.2.Bulk Operations

Bulk operations are performed in the following order:

  1. Upload to Lingotek
  2. Request translations
  3. Download translations

If you select many articles, it will take time, so let's wait be bemish.

7.3.3.Permanent Link Fixes

After this, I would like to reset the featured image of the Japanese article immediately, but before that, let's add "-en" after the slug of the English translation article. The reason is that immediately after the English translation, the English translation page and the Japanese page are the same slug, and the branch number "-2" to avoid duplication is automatically given after the article saved earlier. If this is attached, the URL of the existing Japanese page will change, and if the link is put to the existing page, it will not be able to access it.

7.3.4.Re-registration of eye-catching images

As mentioned earlier, since the featured image of the target article will be removed immediately after the English translation, let's set the eye catch image again from the Japanese version of the article. If you register the featured image in the Japanese version, the English translation version will also be set. Since the same catch image is displayed in Japanese articles and English translation articles, in order to appeal to People in English-speaking countries, it is good to add English as necessary.

7.3.5.Proofreading english translation articles

Be sure to review your English-translated articles. Because the following events occur, there is a possibility that the evaluation of the blog will decrease if you do not review it.

  • Incorrect subject Japanese may be written by omitting the subject, but if translated into English, this subject may be "We". Let's change this if necessary.
  • Custom code collapse The symbol of the tag set in the blog collapses. So let's fix the code to work properly.
  • Media break break The line break that was set for content such as images and video links is often off, and the layout collapses. So let's fix it one by one.
  • Review of the link in the blog If you have posted the link in the blog with a Japanese article and an English article, the slug will change, so let's replace the English translation with an English translation.

Summary

In summary,Polylang is an excellent multilingualization tool, but there were many things to set up before multilingualization was completed, which was quite difficult. In addition, if you do not review the article after the English translation, there is a strange part, so it is necessary to review whether it is in proper English. So, the English translation is quite a hurdle, but as I mentioned at the beginning, there is a possibility that we can reach 1.5 billion people in English-speaking countries, so I think it is worth trying. If you are worried, please try it! Thank you for browsing. So, then(^^)/

  • The person who wrote this article
  • latest article

小林 祐也(ゆーや@ブログ運営者)

In order to solve daily problems, we are planning a mechanism to disseminate life hacks and health care know-how, and to spread the teal organization and value principle that will lead the next era.

-Blog Management