Polyglot · Straightforward I18n for Jekyll Blogs
Description: 크고 작은 블로그 모두가 빠르고 직관적인 다국어 지원을 가능케 하는 i18n 지원 Jekyll 플러그인.
Keywords: 다국어, i18n, 제킬, 다국어, 빠른, 직관적인, untra, 깃허브, 페이지, 블로그, 플러그인, 루비, 젬, 국제화, 현지화, 번역, 언어, 지원, 다국어, 다국어

# Localized variables

29 Feb 2024

Polyglot allows you to have different pages for different languages in your Jekyll site. For example, one could have a page `about.md` in English and another `about.md` in Spanish with completely different layouts. But if you want to have the same layout for both pages, you can use localized variables. This is a way to have different data for different languages in your Jekyll site, but using the same layout for all languages.

As an example I will use a template site created with Polyglot.

## Sharing a layout between pages

In that site they have an about page for every language, in their case english in _pages/en-us/about.md and brazilian portuguese in _pages/pt-br/about.md. In both pages we can see that they have the same keys in the frontmatter, but some with different values. Both files point to the same layout, about, and this layout uses the values in the frontmatter to render the page.

For example, the `subtitle` key in the english page has the value `subtitle: <a href='#'>Affiliations</a>. Address. Contacts. Moto. Etc.` and in the brazilian portuguese page it has `subtitle: <a href='#'>Afiliações</a>. Endereço. Contatos. Lema. Etc.`. To use this information in the layout, it is used like this:

    {{ page.subtitle }}

The same goes for the content below the frontmatter in both files, which is simply used in the layout like this:

    {{ content }}

Polyglot will automatically render the page with the correct values for the current language.

## Sharing a layout between pages with localized data

For the `subtitle` of the page they used `key: value` pairs in the frontmatter, but sometimes we want to use these same pairs in different parts of the site. For example, if we want to use the same `subtitle` in the `about.md` and in another page, we would have to repeat the same pair in the frontmatter of both pages. This is not ideal because if we want to change the `subtitle` we would have to change it in two places. This is where localized data comes in. You can create a file like `_data/:lang/strings.yml`, one for each language, and Polyglot will bring those keys under `site.data[:lang].strings`.

For example, in the template site there are two files, _data/en-us/strings.yml and _data/pt-br/strings.yml. In the first file they have:

    latest_posts: latest posts

And in the second file they have:

    latest_posts: últimas postagens

This way, they can use the `latest_posts` key in the layout like this:

    {{ site.data[site.active_lang].strings.latest_posts }}

Which will correctly get the value for the `latest_posts` variable defined in the file `_data/:lang/strings.yml` for the current language.

## Defining which variable to use in the frontmatter

Now if you want to define this variable in the frontmatter of the page, this gets a little bit trickier. One possible solution is to check if the value of the variable has a `.` in it, and if it does use the value in the file `_data/:lang/strings.yml`. This is how you would do it:

    {% if frontmatter_var contains '.' %}
      {% assign first_part = frontmatter_var | split: '.' | first %}
      {% assign last_part = frontmatter_var | split: '.' | last %}
      {% capture result %}{{ site.data[site.active_lang].strings[first_part][last_part] }}{% endcapture %}
    {% endif %}

    {{ result }}

This will work, for example, if `frontmatter_var = blog.title`.

Now, if you need to check if the localization string (in this case `blog.title`) actually exists in the file `_data/:lang/strings.yml` before using it, you’ll have to create a plugin to check if the variable exists in the file `_data/:lang/strings.yml` and if it does, use it, otherwise fallback to any value you want. I will not go into detail on how to do this, but I will show you how to use it. You can see the code for the plugin here.

    {% if frontmatter_var contains '.' %}
      {% capture contains_localization %}{% localization_exists {{ frontmatter_var }} %}{% endcapture %}
      {% if contains_localization == 'true' %}
        {% assign first_part = frontmatter_var | split: '.' | first %}
        {% assign last_part = frontmatter_var | split: '.' | last %}
        {% capture result %}{{ site.data[site.active_lang].strings[first_part][last_part] }}{% endcapture %}
      {% else %}
        {% capture result %}fallback value{% endcapture %}
      {% endif %}
    {% endif %}

    {{ result }}

# Polyglot 1.7.0 and page_id front-matter for different permalinks by language

29 Oct 2023

I’m excited to announce Jekyll-Polyglot 1.7.0, which has a new feature to give pages language specific permalinks and to retain their association to other relative pages.

This new feature is provided by antoniovazquezblanco, who is a gentleman and a scholar.

## use `page_id` frontmatter to associate pages with different permalinks

Polyglot associates pages by matching their permalinks or filenames. However some site translations may instead desire pages with unique permalinks.

Polyglot already coordinates multiple copes of the same document across different languages. So keying off of a different property like `page_id` is no different than keying off of the permalink.

Using a `page_id` to coordinate similar pages with different permalinks ensures that custom permalinks can still be seen on language specific sites.

### redirects for unique permalinks

The challenge with unique permalinks comes with relativizing those urls. Polyglot avoids this problem entirely by suggesting consistent permalinks.

To help with this, polyglot sets `redirect_from` hidden frontmatter on these pages, listing the unique permalinks of corresponding pages.

When using the `jekyll-redirect-from` plugin, that frontmatter will be picked up, and intelligent redirects made to the page’s custom permalink.

To see this in action, visit this page with a long permalink in different languages.

## Other bug fixes

- This release should have a fix for #151 and #184, preventing crashes on startup when calling other jekyll commands.

# Polyglot 1.6.0 and Simplified Chinese language support

08 Jun 2023

The Polyglot website has been updated with support for Chinese!

This is made possible by aturret, who contributed numerous bugfixes to the plugin, the website, and an entirely new site translation.

Additionally, jekyll-polyglot 1.6.0 is now available from rubygems.

## Fix for relativization of frozen strings

Polyglot used String::gsub! which mutates a `.frozen?` string. This has now been fixed to duplicate the cloned string before modifying it.

## Fix for site navigation not being translated

A typo in the html on the site layout prevented the previous page navigation from being translated correctly.

## Support for Chinese Language

With a big 谢谢 of support and appreciation to aturret, polyglot.untra.io now supports a `zh-CN` Simplified Chinese translation!

# Polyglot 웹 사이트가 이제 한국어로 제공됩니다.

27 Feb 2023

이 웹사이트 한국어 지원으로 업데이트 되었습니다!

이것은 의해 제공됩니다 SalinatedCoffee, 이러한 변화에 기여한 사람. 프로젝트를 도와 주셔서 고마워요!

# Polyglot 1.5.1

01 Oct 2022

Polyglot Release for version 1.5.1.

## Anchor links in relativized urls

With support from dougieh Polyglot will now relativize urls in anchor links.

## Support for Hebrew

Shalom my hebrews and shebrews, Polyglot’s website is now in עברית!

Older Newer