Jekyll-Polyglot 1.8.1이 출시되었습니다. 이번 릴리스에는 몇 가지 기능 개선 사항과 커뮤니티에서 발견된 버그 해결이 포함되어 있습니다.
hacketiwack은 문서 퍼malink 설정을 위한 보다 엄격한 검사를 제공하여 빈 프런트매터 필드로 인한 하류 문제를 방지했습니다.
Github 사용자 blackpill은 기본 언어 링크 대체 href 렌더링 시 i18n 헤더 태그에 대한 단일 문자 버그 수정을 제출했습니다.
몇 가지 기능 향상과 커뮤니티 문서 및 기여를 인정하는 Jekyll-Polyglot 1.8.0에 대해 기대를 높이세요! 몇 가지 기능 향상과 커뮤니티 문서 및 기여를 인정하는 제킬-폴리글롯 1.8.0 에 대해 기대를 높이세요!
한 가지 새로운 기능은 페이지에 언어별 고유 링크를 제공하고 다른 상대 페이지와의 연결을 유지하는 것입니다. 이 새로운 기능은 또 다시 antoniovazquezblanco 에 의해 개선되었습니다, 진실된 신사이면서 학식 있는 분입니다.
이 릴리스는 또한 품질을 인정합니다 sitemap.xml 그리고 robots.txt solution provided by jerturowetz. 이 사이트는 이제 검색 엔진에 의해 정적 제킬 웹사이트로 크롤링될 수 있도록 이러한 설정을 사용하여 더 많은 SEO 기능을 보여주고 활용합니다. 여기 예시 웹사이트 파일을 참조하십시오.
Github 사용자 obfusk 몇 년 전 작은 기여를 했습니다 기여를 했습니다.
을 사용하여 polyglot :site, :post_write 이 기능은 각 자식 프로세스 실행 시 한 번 실행됩니다:
Jekyll::Hooks.register :site, :post_write do |site|
...
end
이 릴리스는 모든 언어가 처리된 후 정확히 한 번 실행되는 사용자 정의 후크 :post_write 를 추가합니다 (여부 parallel_localization 사용됩니다):
Jekyll::Hooks.register :polyglot, :post_write do |site|
# 여기서 놀라운 것을 만들어 보세요!
end
이 기능은 추가적인 활용이 필요한 복잡한 제킬 정적 사이트에 유용합니다 jekyll hook plugins.
그녀는 또한 다음과 같은 문제를 해결하는 언어 서브 프로세스 충돌 시 추가 로깅. 이 기여에 감사합니다!
george-gca 재능이 뛰어나고 멋진 분입니다, 그는 전체 블로그 게시물을 기고했습니다 웹사이트 데이터에서 리치 텍스트를 가장 효과적으로 로컬라이징하는 방법에 대한. 그는 또한 제공했습니다 브라질 포르투갈어 사이트 번역.
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.
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.
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.
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 }}
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.
page_id frontmatter to associate pages with different permalinksPolyglot 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.
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.
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.
Polyglot used String::gsub! which mutates a .frozen? string. This has now been fixed to duplicate the cloned string before modifying it.
A typo in the html on the site layout prevented the previous page navigation from being translated correctly.
With a big 谢谢 of support and appreciation to aturret, polyglot.untra.io now supports a zh-CN Simplified Chinese translation!