Polyglot 1.3.3
19 Jul 2020Polyglot version 1.3.3 is out! It includes a minor fix for when running jekyll serve --incremental
with polyglot installed on a fresh build.
This release was made possible with the support of the following github user!
Polyglot version 1.3.3 is out! It includes a minor fix for when running jekyll serve --incremental
with polyglot installed on a fresh build.
This release was made possible with the support of the following github user!
Polyglot version 1.3.2 has been released! Give it a try!
This release was made possible with the support of the following github user
lang_from_path
setting to derive document lang from relative pathThis release adds a new boolean configuration setting lang_from_path
. When set to true, this option tells polyglot to derive the base language from a matching subpath if the lang frontmatter is not set. This setting works well in conjunction with other translation maintenance tools such as po4a.
excluded_from_localization
files will have trailing slashes added to their paths if they are directories. In addition, these files will be matched differently in the relativize and absolute url regex matchers. This will improve the accuracy of url relativization based on user feedback.
A new version of Polyglot has been released! Give it a try!
This release was made possible with the support of the following github users:
site.data
Language specific content defined in your site.data
directory will now be recursively merged together, so that active_lang
content gets precedence over default_lang
content, gets precedence over language non-specific content. (#59)
default_lang
site rootIf the default_lang
is not defined in the languages
, this ensures that language unassigned files (such as those excluded from localization) are still written out to the site root. (#65)
i18n_headers
tagDocument processing is now faster, and fixes were made to the i18n_headers for when the site.url is defined. (#67)
active_lang
site payloadThis allows custom keys to be defined with the active_lang
, giving interoperability between polyglot and other plugins and themes. (#68)
A new version of Polyglot has been released! Give it a try!
This release was made possible due to the kind support of github user vlsi, who helped fix a few bugs and added new features:
Polyglot will now translate your site.url
, so absolute urls will now get translated as well.
Jekyll collections are a fairly new feature. This update translates all registered collections, not just site posts and pages.
_data
for site.data
rich text when site.data[:lang]
is presentTop level rich text organized by language will be assigned to the site.data when building. Before, when rendering rich text, you would have to use:
Now rich text can be rendered with just:
I18n_Headers
tag now defaults to site.url
when left blankUsers can now use
without specifying a url, defaulting it to your site.url
A new version of Polyglot has been released! Give it a try!
and list jekyll-polyglot
among your listed gems in your _config.yml
It involves mostly groundwork to prepare for new features and better multilingual content management. It does have a new feature:
Put this tag with the url of your website in your head.html
includes file to get the maximum SEO provided by having a multilingual website. It’s the same as the following liquid code:
In your header, but faster and cleaner! For more information, see the SEO page