Nous sommes un restaurant situé à Paris . Ceci est notre menu.
Nous sommes un restaurant situé à Paris . Ceci est notre menu.
Cliquez ici pour aller à l'entrée du site.
```
#### Disabling Url Relativizing
_New in 1.4.0_
If you dont want a href attribute to be relativized (such as for making [a language switcher](https://github.com/untra/polyglot/blob/master/site/_includes/sidebar.html#L40)), you can use the `{% static_href %}href="..."{% endstatic_href %}` block tag.
```html
click this static link
```
that will generate `click this static link` which is what you would normally use to create a url unmangled by invisible language relativization.
Combine with a [html minifier](https://github.com/digitalsparky/jekyll-minifier) for a polished and production ready website.
#### Exclusive site language generation
_New in 1.4.0_
If you want to control which languages a document can be generated for, you can specify `lang-exclusive: [ ]` frontmatter.
If you include this frontmatter in your post, it will only generate for the specified site languages.
For Example, the following frontmatter will only generate in the `en` and `fr` site language builds:
```
---
lang-exclusive: ['en', 'fr']
---
```
#### Machine-aware site building
_New in 1.5.0_
Polyglot will only start builds after it confirms there is a cpu core ready to accept the build thread. This ensures that jekll will build large sites efficiently streamlining build processes instead of overloading machines with process thrash.
#### Localized site.data
There are cases when `site.data` localization is required.
For instance: you might need to localize `_data/navigation.yml` that holds "navigation menu".
In order to localize it, just place language-specific files in `_data/:lang/...` folder, and Polyglot will bring those keys to the top level.
## How It Works
This plugin makes modifications to existing Jekyll classes and modules, namely `Jekyll::StaticFile` and `Jekyll::Site`. These changes are as lightweight and slim as possible. The biggest change is in `Jekyll::Site.process`. Polyglot overwrites this method to instead spawn a separate process for each language you intend to process the site for. Each of those processes calls the original `Jekyll::Site.process` method with its language in mind, ensuring your website scales to support any number of languages, while building all of your site languages simultaneously.
`Jekyll::Site.process` is the entry point for the Jekyll build process. Take care whatever other plugins you use do not also attempt to overwrite this method. You may have problems.
## Features
This plugin stands out from other I18n Jekyll plugins.
- automatically corrects your relative links, keeping your *french* visitors on your *french* website, even when content has to fallback to the `default_lang`.
- builds all versions of your website *simultaneously*, allowing big websites to scale efficiently.
- provides the liquid tag `{{ site.languages }}` to get an array of your I18n strings.
- provides the liquid tag `{{ site.default_lang }}` to get the default_lang I18n string.
- provides the liquid tag `{{ site.active_lang }}` to get the I18n language string the website was built for. Alternative names for `active_lang` can be configured via `config.lang_vars`.
- provides the liquid tag `{{ I18n_Headers https://yourwebsite.com/ }}` to append SEO bonuses to your website.
- provides the liquid tag `{{ Unrelativized_Link href="/hello" }}` to make urls that do not get influenced by url correction regexs.
- provides `site.data` localization for efficient rich text replacement.
- a creator that will answer all of your questions and issues.
## SEO Recipes
Jekyll-polyglot has a few spectacular [Search Engine Optimization techniques](https://untra.github.io/polyglot/seo) to ensure your Jekyll blog gets the most out of it's multilingual audience. Check them out!
### Other Websites Built with Polyglot
Feel free to open a PR and list your multilingual blog here you may want to share:
* [Polyglot project website](https://polyglot.untra.io)
* [LogRhythm Corporate Website](https://logrhythm.com)
* [All Over Earth](https://allover.earth/)
* [Hanare Cafe in Toshijima, Japan](https://hanarecafe.com)
* [F-Droid](https://f-droid.org)
* [Ubuntu MATE](https://ubuntu-mate.org)
## Compatibility
Currently supports Jekyll 3.0 , and Jekyll 4.0
* Windows users will need to disable parallel_localization on their machines by setting `parallel_localization: false` in the `_config.yml`
* In Jekyll 4.0 , SCSS source maps will generate improperly due to how Polyglot operates. The workaround is to disable the CSS sourcemaps. Adding the following to your `config.yml` will disable sourcemap generation:
```yaml
sass:
sourcemap: never
```
## Contributions
Please! I need all the support I can get! 🙏
But for real I would appreciate any contributions and support. This started as an open-source side-project and has gotten bigger than I'd ever imagine!
If you have something you'd like to contribute to jekyll-polyglot, please open a PR!
## 2.0 Roadmap
* [ ] - **site language**: portuguese `pt_BR` `pt_PT`
* [ ] - **site language**: arabic `ar`
* [ ] - **site language**: japanese `ja`
* [x] - **site language**: russian `ru`
* [ ] - **site language**: korean `ko`
* [ ] - **site language**: hebrew `he`
* [ ] - get whitelisted as an official github-pages jekyll plugin
* [x] - update CI provider
## Copyright
Copyright (c) Samuel Volin 2021. License: MIT
polyglot-1.5.0/Rakefile 0000664 0000000 0000000 00000000131 14074562261 0015035 0 ustar 00root root 0000000 0000000 require "rspec/core/rake_task"
RSpec::Core::RakeTask.new(:spec)
task :default => [:spec]
polyglot-1.5.0/jekyll-polyglot.gemspec 0000664 0000000 0000000 00000001107 14074562261 0020102 0 ustar 00root root 0000000 0000000 Gem::Specification.new do |s|
s.name = 'jekyll-polyglot'
s.version = '1.5.0'
s.date = '2021-07-17'
s.summary = 'I18n plugin for Jekyll Blogs'
s.description = 'Fast open source i18n plugin for Jekyll blogs.'
s.authors = ['Samuel Volin']
s.email = 'untra.sam@gmail.com'
s.files = ['README.md', 'LICENSE'] + Dir['lib/**/*']
s.homepage = 'https://polyglot.untra.io/'
s.license = 'MIT'
s.add_runtime_dependency('jekyll', '>= 3.0')
s.required_ruby_version = '>= 2.4.0'
s.required_rubygems_version = '>= 2.7.0'
end
polyglot-1.5.0/lib/ 0000775 0000000 0000000 00000000000 14074562261 0014143 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll-polyglot.rb 0000664 0000000 0000000 00000000032 14074562261 0017624 0 ustar 00root root 0000000 0000000 require "jekyll/polyglot"
polyglot-1.5.0/lib/jekyll/ 0000775 0000000 0000000 00000000000 14074562261 0015435 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot.rb 0000664 0000000 0000000 00000000237 14074562261 0017635 0 ustar 00root root 0000000 0000000 require 'jekyll'
require_relative 'polyglot/liquid'
require_relative 'polyglot/patches'
require_relative 'polyglot/hooks'
require_relative 'polyglot/version'
polyglot-1.5.0/lib/jekyll/polyglot/ 0000775 0000000 0000000 00000000000 14074562261 0017306 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot/hooks.rb 0000664 0000000 0000000 00000000105 14074562261 0020752 0 ustar 00root root 0000000 0000000 require_relative 'hooks/coordinate'
require_relative 'hooks/process'
polyglot-1.5.0/lib/jekyll/polyglot/hooks/ 0000775 0000000 0000000 00000000000 14074562261 0020431 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot/hooks/assets-toggle.rb 0000664 0000000 0000000 00000000332 14074562261 0023535 0 ustar 00root root 0000000 0000000 # Jekyll::Hooks.register :site, :after_init do |site|
# if site.config['assets']
# if site.active_lang != site.default_lang
# then jekyll.sprockets.asset_config['autowrite'] = false
# end
# end
# end
polyglot-1.5.0/lib/jekyll/polyglot/hooks/coordinate.rb 0000664 0000000 0000000 00000001656 14074562261 0023115 0 ustar 00root root 0000000 0000000 # hook to coordinate blog posts and pages into distinct urls,
# and remove duplicate multilanguage posts and pages
Jekyll::Hooks.register :site, :post_read do |site|
hook_coordinate(site)
end
def hook_coordinate(site)
# Copy the language specific data, by recursively merging it with the default data.
# Favour active_lang first, then default_lang, then any non-language-specific data.
# See: https://www.ruby-forum.com/topic/142809
merger = proc { |key, v1, v2| Hash === v1 && Hash === v2 ? v1.merge(v2, &merger) : v2 }
if site.data.include?(site.default_lang)
site.data = site.data.merge(site.data[site.default_lang], &merger)
end
if site.data.include?(site.active_lang)
site.data = site.data.merge(site.data[site.active_lang], &merger)
end
site.collections.each do |_, collection|
collection.docs = site.coordinate_documents(collection.docs)
end
site.pages = site.coordinate_documents(site.pages)
end
polyglot-1.5.0/lib/jekyll/polyglot/hooks/process.rb 0000664 0000000 0000000 00000000441 14074562261 0022433 0 ustar 00root root 0000000 0000000 # hook to make a call to process rendered documents,
Jekyll::Hooks.register :site, :post_render do |site|
hook_process(site)
end
def hook_process(site)
site.collections.each do |_, collection|
site.process_documents(collection.docs)
end
site.process_documents(site.pages)
end
polyglot-1.5.0/lib/jekyll/polyglot/liquid.rb 0000664 0000000 0000000 00000000247 14074562261 0021125 0 ustar 00root root 0000000 0000000 module Jekyll
module Polyglot
module Liquid
require_relative 'liquid/tags/i18n_headers'
require_relative 'liquid/tags/static_href'
end
end
end
polyglot-1.5.0/lib/jekyll/polyglot/liquid/ 0000775 0000000 0000000 00000000000 14074562261 0020575 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot/liquid/tags/ 0000775 0000000 0000000 00000000000 14074562261 0021533 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot/liquid/tags/i18n_headers.rb 0000664 0000000 0000000 00000002130 14074562261 0024326 0 ustar 00root root 0000000 0000000 module Jekyll
module Polyglot
module Liquid
class I18nHeadersTag < ::Liquid::Tag
def initialize(tag_name, text, tokens)
super
@url = text
@url.strip!
@url.chomp! '/'
end
def render(context)
site = context.registers[:site]
permalink = context.registers[:page]['permalink']
site_url = @url.empty? ? site.config['url'] : @url
i18n = "\n"
i18n += "\n"
site.languages.each do |lang|
next if lang == site.default_lang
i18n += "\n"
end
i18n
end
end
end
end
end
Liquid::Template.register_tag('I18n_Headers', Jekyll::Polyglot::Liquid::I18nHeadersTag)
Liquid::Template.register_tag('i18n_headers', Jekyll::Polyglot::Liquid::I18nHeadersTag)
polyglot-1.5.0/lib/jekyll/polyglot/liquid/tags/static_href.rb 0000664 0000000 0000000 00000002021 14074562261 0024346 0 ustar 00root root 0000000 0000000 module Jekyll
module Polyglot
module Liquid
class StaticHrefTag < :: Liquid::Block
def initialize(tag_name, params, tokens)
super
end
def render(context)
text = super
href_attrs = text.strip.split '='
valid = (href_attrs.length == 2 && href_attrs[0] == 'href') && href_attrs[1].start_with?('"') && href_attrs[1].end_with?('"')
unless valid
raise Liquid::SyntaxError, "static_href parameters must include match href=\"...\" attribute param, eg. href=\"http://example.com\, href=\"/about\", href=\"/\" , instead got:\n#{text}"
end
href_value = href_attrs[1]
# href writes out as ferh="..." explicitly wrong, to be cauaght by seperate processor for nonrelativized links
"ferh=#{href_value}"
end
end
end
end
end
Liquid::Template.register_tag('Static_Href', Jekyll::Polyglot::Liquid::StaticHrefTag)
Liquid::Template.register_tag('static_href', Jekyll::Polyglot::Liquid::StaticHrefTag)
polyglot-1.5.0/lib/jekyll/polyglot/patches.rb 0000664 0000000 0000000 00000000125 14074562261 0021260 0 ustar 00root root 0000000 0000000 require_relative 'patches/jekyll/site'
require_relative 'patches/jekyll/static_file'
polyglot-1.5.0/lib/jekyll/polyglot/patches/ 0000775 0000000 0000000 00000000000 14074562261 0020735 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot/patches/jekyll/ 0000775 0000000 0000000 00000000000 14074562261 0022227 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/lib/jekyll/polyglot/patches/jekyll/site.rb 0000664 0000000 0000000 00000016756 14074562261 0023537 0 ustar 00root root 0000000 0000000 require 'etc'
include Process
module Jekyll
class Site
attr_reader :default_lang, :languages, :exclude_from_localization, :lang_vars
attr_accessor :file_langs, :active_lang
def prepare
@file_langs = {}
fetch_languages
@parallel_localization = config.fetch('parallel_localization', true)
@lang_from_path = config.fetch('lang_from_path', false)
@exclude_from_localization = config.fetch('exclude_from_localization', []).map do |e|
if File.directory?(e) && e[-1] != '/'
e + '/'
else
e
end
end
end
def fetch_languages
@default_lang = config.fetch('default_lang', 'en')
@languages = config.fetch('languages', ['en']).uniq
@keep_files += (@languages - [@default_lang])
@active_lang = @default_lang
@lang_vars = config.fetch('lang_vars', [])
end
alias_method :process_orig, :process
def process
prepare
all_langs = (@languages + [@default_lang]).uniq
if @parallel_localization
nproc = Etc.nprocessors
pids = {}
begin
all_langs.each do |lang|
pids[lang] = fork do
process_language lang
end
while pids.length >= (lang == all_langs[-1] ? 1 : nproc)
sleep 0.1
pids.map do |lang, pid|
pids.delete lang if waitpid pid, Process::WNOHANG
end
end
end
rescue Interrupt
all_langs.each do |lang|
next unless pids.key? lang
puts "Killing #{pids[lang]} : #{lang}"
kill('INT', pids[lang])
end
end
else
all_langs.each do |lang|
process_language lang
end
end
end
alias_method :site_payload_orig, :site_payload
def site_payload
payload = site_payload_orig
payload['site']['default_lang'] = default_lang
payload['site']['languages'] = languages
payload['site']['active_lang'] = active_lang
lang_vars.each do |v|
payload['site'][v] = active_lang
end
payload
end
def process_language(lang)
@active_lang = lang
config['active_lang'] = @active_lang
lang_vars.each do |v|
config[v] = @active_lang
end
if @active_lang == @default_lang
then process_default_language
else process_active_language
end
end
def process_default_language
old_include = @include
process_orig
@include = old_include
end
def process_active_language
old_dest = @dest
old_exclude = @exclude
@file_langs = {}
@dest = @dest + '/' + @active_lang
@exclude += @exclude_from_localization
process_orig
@dest = old_dest
@exclude = old_exclude
end
def derive_lang_from_path(doc)
if !@lang_from_path
return nil
end
segments = doc.relative_path.split('/')
if doc.relative_path[0] == '_' \
&& segments.length > 2 \
&& segments[1] =~ /^[a-z]{2,3}(:?[_-](:?[A-Za-z]{2}){1,2}){0,2}$/
return segments[1]
elsif segments.length > 1 \
&& segments[0] =~ /^[a-z]{2,3}(:?[_-](:?[A-Za-z]{2}){1,2}){0,2}$/
return segments[0]
else
return nil
end
end
# assigns natural permalinks to documents and prioritizes documents with
# active_lang languages over others. If lang is not set in front matter,
# then this tries to derive from the path, if the lang_from_path is set.
# otherwise it will assign the document to the default_lang
def coordinate_documents(docs)
regex = document_url_regex
approved = {}
docs.each do |doc|
lang = doc.data['lang'] || derive_lang_from_path(doc) || @default_lang
lang_exclusive = doc.data['lang-exclusive'] || []
url = doc.url.gsub(regex, '/')
doc.data['permalink'] = url
# skip this document if it has already been processed
next if @file_langs[url] == @active_lang
# skip this document if it has a fallback and it isn't assigned to the active language
next if @file_langs[url] == @default_lang && lang != @active_lang
# skip this document if it has lang-exclusive defined and the active_lang is not included
next if !lang_exclusive.empty? && !lang_exclusive.include?(@active_lang)
approved[url] = doc
@file_langs[url] = lang
end
approved.values
end
# performs any necesarry operations on the documents before rendering them
def process_documents(docs)
# return if @active_lang == @default_lang
url = config.fetch('url', false)
rel_regex = relative_url_regex(false)
abs_regex = absolute_url_regex(url, false)
non_rel_regex = relative_url_regex(true)
non_abs_regex = absolute_url_regex(url, true)
docs.each do |doc|
unless @active_lang == @default_lang then relativize_urls(doc, rel_regex) end
correct_nonrelativized_urls(doc, non_rel_regex)
if url
unless @active_lang == @default_lang then relativize_absolute_urls(doc, abs_regex, url) end
correct_nonrelativized_absolute_urls(doc, non_abs_regex, url)
end
end
end
# a regex that matches urls or permalinks with i18n prefixes or suffixes
# matches /en/foo , .en/foo , foo.en/ and other simmilar default urls
# made by jekyll when parsing documents without explicitly set permalinks
def document_url_regex
regex = ''
@languages.each do |lang|
regex += "([\/\.]#{lang}[\/\.])|"
end
regex.chomp! '|'
%r{#{regex}}
end
# a regex that matches relative urls in a html document
# matches href="baseurl/foo/bar-baz" href="/foo/bar-baz" and others like it
# avoids matching excluded files. prepare makes sure
# that all @exclude dirs have a trailing slash.
def relative_url_regex(disabled = false)
regex = ''
unless disabled
@exclude.each do |x|
regex += "(?!#{x})"
end
@languages.each do |x|
regex += "(?!#{x}\/)"
end
end
start = disabled ? 'ferh' : 'href'
%r{#{start}=\"?#{@baseurl}\/((?:#{regex}[^,'\"\s\/?\.#]+\.?)*(?:\/[^\]\[\)\(\"\'\s]*)?)\"}
end
# a regex that matches absolute urls in a html document
# matches href="http://baseurl/foo/bar-baz" and others like it
# avoids matching excluded files. prepare makes sure
# that all @exclude dirs have a trailing slash.
def absolute_url_regex(url, disabled = false)
regex = ''
unless disabled
@exclude.each do |x|
regex += "(?!#{x})"
end
@languages.each do |x|
regex += "(?!#{x}\/)"
end
end
start = disabled ? 'ferh' : 'href'
%r{(?
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
After months of work and refinement, I am proud to present Polyglot: a i18n plugin for Jekyll sites that need to cater their content to multiple languages and audiences.
While there are other multi-language plugins for Jekyll, Polyglot is special. Polyglot takes care of the typical cruftwork normally left to developers to manage (such as wrangling urls and ensuring consistent sitemaps) while providing efficient and simple tools Jekyll developers can utilize into SEO and fast-tracked content aggregation.
In the past, a multi-language static site or blog had to keep delicate track of what language each relative link the site was serving. It was all too easy for a developer to stumble, and foreign language visitors would quickly get lost in untranslated content.
Polyglot automatically relativizes the urls for each language you want your site to build for. This allows website visitors to stay isolated on one language while browsing your website.
When you don’t have translated or multilingual content, Jekyll will still build with the content you do have. When you do have translated or multilingual content, Jekyll will build using that content. Simple as that.
Sitemaps stay consistent across all languages, and translated stays in the site it was built for.
Rich language content is normally hard to implement. Short strings or language dependent banners are typically hard for a Jekyll website to keep consistent.
Except when it’s this easy. In your config.yml, just store your strings as:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!and in your liquid, just call:
{{ site.hello[site.active_lang]}}produces:
Polyglot will build your multi-language website just as fast as it will build your default language website. Polyglot runs with a minimal overhead by simultaneously building all languages of your website as separate process. This means your website build time won’t be a function of how many languages you need to support.
Polyglot is available as a gem, or as a Jekyll plugin. It can be installed with:
gem install 'jekyll-polyglot'
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotand 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:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}In your header, but faster and cleaner! For more information, see the SEO page
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis release was made possible with the support of the following github users:
site.dataLanguage 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)
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefThis release provides a new liquid block tag {% static_href %}href=”…”{% endstatic_href %} which can be used to create href attributes in anchor tags that are not relativized by Polyglot.
Jekyll-Polyglot is fairly greedy and naive in it’s relativization, and so if you want a url that is explicitly static (such as for making a language switcher, hint hint), this liquid tag will help you construct that unmangled href=”…” tag in anchor elements.
Polyglot 1.4.0 adds support for lang-exclusive: [ ] frontmatter in documents. If added to a document, this frontmatter will limit generation of the document to that specific language.
---
lang-exclusive: ['en']
---This is a way to control which languages may see a document, even if that document may not have an equivalent in the default language site.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Bonus patch release of Polyglot version 1.4.1 is out!
Fallout from cleanup led to a small fix and some tests
Russian language site pages have been added!
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Polyglot Release for version version 1.5.0, with new support for staggered builds by logical cpus.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Has Polyglot helped your website expand into new territories and markets? Do you have a suggestion, contribution or bugfix you’d like to provide? Want to see this website translated into your native language?
Drop me a line, open a issues or make a PR! All support and contributions are greatly appreciated.
This permalink is really long and complex
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Nach monatelanger Arbeit und Raffinesse, ich bin stolz darauf, Polyglot präsentieren: eine i18n-Plugin für Jekyll Websites, die Notwendigkeit, ihre Inhalte in mehrere Sprachen und Zielgruppen gerecht zu werden.
Zwar gibt es andere Multi-Language-Plugins für Jekyll ist Polyglot Besonderes. Polyglot kümmert sich um den typischen Unsinn in der Regel an die Entwickler verlassen zu verwalten (wie Gerangel URLs und konsistente Sitemaps) und bietet effiziente und einfache Werkzeuge Jekyll-Entwickler können in SEO und Eilverfahren Content-Aggregation zu nutzen.
In der Vergangenheit hatte eine mehrsprachige statische Website oder ein Blog, um empfindliche verfolgen, was die Sprache jedes relativen Link wurde die Website dient zu halten. Es war viel zu einfach für einen Entwickler zu stolpern, und Fremdsprachen Besucher würde schnell in nicht übersetzten Inhalte verloren gehen.
Polyglot relativiert automatisch die URLs für jede Sprache, die Sie Ihre Website, um für die bauen wollen. Dies ermöglicht es Website-Besucher zu isoliert auf eine Sprache zu bleiben, während Durchsuchen Ihrer Website.
Wenn Sie nicht haben übersetzt oder mehrsprachige Inhalte, Jekyll wird immer noch mit dem Inhalt zu bauen Sie zu tun haben. Wenn Sie müssen haben übersetzt oder mehrsprachigen Inhalten wird Jekyll bauen mit diesem Inhalt. So einfach ist das.
Sitemaps bleiben konsistent über alle Sprachen und übersetzt Aufenthalte in der Website es gebaut wurde.
Reiche Sprache Inhalt ist in der Regel schwer zu implementieren. Kurze Strings oder sprachabhängige Banner sind in der Regel schwer für einen Jekyll Website konsistent zu halten.
Außer, wenn es so einfach. In Ihrem config.yml, nur die Saiten zu speichern, wie:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!und in ihre liquid, einfach anrufen:
{{ site.hello[site.active_lang]}}produziert:
Polyglot wird Ihre mehrsprachige Website genauso schnell zu bauen, wie es Ihre Standardsprache Website zu bauen. Polyglot läuft mit einem minimalen Overhead von gleichzeitig Gebäude alle Sprachen Ihrer Website als separaten Prozess. Das bedeutet, Ihre Website Build-Zeit wird nicht davon ab, wie viele Sprachen, die unterstützt werden müssen.
Polyglot ist als eines ruby gem oder als Jekyll Plugin. Es kann mit installiert werden:
gem install 'jekyll-polyglot'
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'Eine neue Version von Polyglot wurde veröffentlicht! Versuche es!
gem install jekyll-polyglotund eine Liste jekyll-polyglot unter Ihren aufgelisteten Edelsteine in Ihrer _config.yml
Es geht vor allem Grundstein für neue Funktionen und eine bessere Verwaltung mehrsprachiger Inhalte vorzubereiten. Er hat eine neue Funktion:
Setzen Sie diesen Tag mit der url Ihrer Website in Ihrem head.html enthält Datei die maximale SEO zu erhalten, die von mit einer mehrsprachigen Website. Es ist die gleiche wie die folgende Flüssigkeit Code:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}In der Kopfzeile, aber schneller und sauberer! Weitere Informationen finden Sie unter die SEO-Seite
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
Eine neue Version von Polyglot wurde veröffentlicht! Versuche es!
gem install jekyll-polyglotDiese Freigabe wurde mit der Unterstützung der folgenden github Benutzer ermöglicht:
site.dataSprachspezifische Inhalte, die in Ihrem site.data-Verzeichnis definiert sind, werden nun rekursiv zusammengeführt, so dass active_lang inhalt bekommt Vorrang vor default_lang inhalt, bekommt Vorrang vor kein sprachinhalt. (#59)
default_lang standort rootWenn das default_lang nicht in den languages definiert ist, stellt dies sicher, dass nicht zugewiesene Dateien (wie die von der Lokalisierung ausgeschlossenen) noch nicht auf den Standort root geschrieben werden. (#65)
i18n_headers tagDie Dokumentenverarbeitung ist jetzt schneller und es wurden Korrekturen an der i18n_headers vorgenommen, wenn die Site.url definiert ist. (#67)
active_lang site-nutzlastDamit können benutzerdefinierte Schlüssel mit dem active_lang definiert werden, was die Interoperabilität zwischen polyglot und anderen Plugins und Themen ermöglicht. (#68)
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefDiese Version bietet eine neue liquid block tag {% static_href %}href=”…”{% endstatic_href %} die verwendet werden kann, um zu erstellen href attributes in anchor tags das sind nicht relativiert von Polyglot.
Jekyll-Polyglot ist ziemlich gierig und naiv in seiner Relativierung, und wenn Sie also eine URL wollen, die explizit statisch ist (wie für einen Sprachumschalter machen, apropos), dies liquid tag will helfen Sie, das entwirrt zu konstruieren href=”…” tag in anchor elements.
Polyglot 1.4.0 fügt Unterstützung für lang-exclusive: [ ] frontmaterie in Dokumenten. Wenn dieses Dokument einem Dokument hinzugefügt wird, beschränkt es die Generierung des Dokuments auf diese bestimmte Sprache.
---
lang-exclusive: ['de']
---Auf diese Weise können Sie steuern, in welchen Sprachen ein Dokument angezeigt werden kann, auch wenn dieses Dokument auf der Standardsprachensite möglicherweise keine Entsprechung aufweist.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
Ich suche Freiwillige, die das sehen möchten Jekyll-Polyglot homepage in Ihrer Herkunftssprache vertreten! Wenn Sie diese Software hilfreich finden und Ihre Sprache dargestellt sehen möchten, wenden Sie sich einfach an github issues.
Bonus patch release of Polyglot version 1.4.1 is out!
Fallout from cleanup led to a small fix and some tests
Russian language site pages have been added!
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Polyglot-Release für Version version 1.5.0, mit neuer Unterstützung für gestaffelte Builds durch logische CPU.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Hat Polyglot geholfen Ihre Website in neue Gebiete und Märkte expandieren? Haben Sie einen Vorschlag, Beitrag oder Bugfix, den Sie bereitstellen möchten? Möchten Sie diese Website in Ihre Muttersprache übersetzt sehen?
Drop me a line, open a issues or make a PR!
Alle Unterstützung und Beiträge werden sehr geschätzt.
Permalink ist wirklich lang und komplex
Polyglot-Release für Version version 1.5.0, mit neuer Unterstützung für gestaffelte Builds durch logische CPU.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Hat Polyglot geholfen Ihre Website in neue Gebiete und Märkte expandieren? Haben Sie einen Vorschlag, Beitrag oder Bugfix, den Sie bereitstellen möchten? Möchten Sie diese Website in Ihre Muttersprache übersetzt sehen?
Drop me a line, open a issues or make a PR!
Alle Unterstützung und Beiträge werden sehr geschätzt.
Bonus patch release of Polyglot version 1.4.1 is out!
Fallout from cleanup led to a small fix and some tests
Russian language site pages have been added!
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefDiese Version bietet eine neue liquid block tag {% static_href %}href=”…”{% endstatic_href %} die verwendet werden kann, um zu erstellen href attributes in anchor tags das sind nicht relativiert von Polyglot.
Jekyll-Polyglot ist ziemlich gierig und naiv in seiner Relativierung, und wenn Sie also eine URL wollen, die explizit statisch ist (wie für einen Sprachumschalter machen, apropos), dies liquid tag will helfen Sie, das entwirrt zu konstruieren href=”…” tag in anchor elements.
Polyglot 1.4.0 fügt Unterstützung für lang-exclusive: [ ] frontmaterie in Dokumenten. Wenn dieses Dokument einem Dokument hinzugefügt wird, beschränkt es die Generierung des Dokuments auf diese bestimmte Sprache.
---
lang-exclusive: ['de']
---Auf diese Weise können Sie steuern, in welchen Sprachen ein Dokument angezeigt werden kann, auch wenn dieses Dokument auf der Standardsprachensite möglicherweise keine Entsprechung aufweist.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
Ich suche Freiwillige, die das sehen möchten Jekyll-Polyglot homepage in Ihrer Herkunftssprache vertreten! Wenn Sie diese Software hilfreich finden und Ihre Sprache dargestellt sehen möchten, wenden Sie sich einfach an github issues.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
Eine neue Version von Polyglot wurde veröffentlicht! Versuche es!
gem install jekyll-polyglotDiese Freigabe wurde mit der Unterstützung der folgenden github Benutzer ermöglicht:
site.dataSprachspezifische Inhalte, die in Ihrem site.data-Verzeichnis definiert sind, werden nun rekursiv zusammengeführt, so dass active_lang inhalt bekommt Vorrang vor default_lang inhalt, bekommt Vorrang vor kein sprachinhalt. (#59)
default_lang standort rootWenn das default_lang nicht in den languages definiert ist, stellt dies sicher, dass nicht zugewiesene Dateien (wie die von der Lokalisierung ausgeschlossenen) noch nicht auf den Standort root geschrieben werden. (#65)
i18n_headers tagDie Dokumentenverarbeitung ist jetzt schneller und es wurden Korrekturen an der i18n_headers vorgenommen, wenn die Site.url definiert ist. (#67)
active_lang site-nutzlastDamit können benutzerdefinierte Schlüssel mit dem active_lang definiert werden, was die Interoperabilität zwischen polyglot und anderen Plugins und Themen ermöglicht. (#68)
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
Eine neue Version von Polyglot wurde veröffentlicht! Versuche es!
gem install jekyll-polyglotund eine Liste jekyll-polyglot unter Ihren aufgelisteten Edelsteine in Ihrer _config.yml
Es geht vor allem Grundstein für neue Funktionen und eine bessere Verwaltung mehrsprachiger Inhalte vorzubereiten. Er hat eine neue Funktion:
Setzen Sie diesen Tag mit der url Ihrer Website in Ihrem head.html enthält Datei die maximale SEO zu erhalten, die von mit einer mehrsprachigen Website. Es ist die gleiche wie die folgende Flüssigkeit Code:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}In der Kopfzeile, aber schneller und sauberer! Weitere Informationen finden Sie unter die SEO-Seite
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'Nach monatelanger Arbeit und Raffinesse, ich bin stolz darauf, Polyglot präsentieren: eine i18n-Plugin für Jekyll Websites, die Notwendigkeit, ihre Inhalte in mehrere Sprachen und Zielgruppen gerecht zu werden.
Zwar gibt es andere Multi-Language-Plugins für Jekyll ist Polyglot Besonderes. Polyglot kümmert sich um den typischen Unsinn in der Regel an die Entwickler verlassen zu verwalten (wie Gerangel URLs und konsistente Sitemaps) und bietet effiziente und einfache Werkzeuge Jekyll-Entwickler können in SEO und Eilverfahren Content-Aggregation zu nutzen.
In der Vergangenheit hatte eine mehrsprachige statische Website oder ein Blog, um empfindliche verfolgen, was die Sprache jedes relativen Link wurde die Website dient zu halten. Es war viel zu einfach für einen Entwickler zu stolpern, und Fremdsprachen Besucher würde schnell in nicht übersetzten Inhalte verloren gehen.
Polyglot relativiert automatisch die URLs für jede Sprache, die Sie Ihre Website, um für die bauen wollen. Dies ermöglicht es Website-Besucher zu isoliert auf eine Sprache zu bleiben, während Durchsuchen Ihrer Website.
Wenn Sie nicht haben übersetzt oder mehrsprachige Inhalte, Jekyll wird immer noch mit dem Inhalt zu bauen Sie zu tun haben. Wenn Sie müssen haben übersetzt oder mehrsprachigen Inhalten wird Jekyll bauen mit diesem Inhalt. So einfach ist das.
Sitemaps bleiben konsistent über alle Sprachen und übersetzt Aufenthalte in der Website es gebaut wurde.
Reiche Sprache Inhalt ist in der Regel schwer zu implementieren. Kurze Strings oder sprachabhängige Banner sind in der Regel schwer für einen Jekyll Website konsistent zu halten.
Außer, wenn es so einfach. In Ihrem config.yml, nur die Saiten zu speichern, wie:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!und in ihre liquid, einfach anrufen:
{{ site.hello[site.active_lang]}}produziert:
Polyglot wird Ihre mehrsprachige Website genauso schnell zu bauen, wie es Ihre Standardsprache Website zu bauen. Polyglot läuft mit einem minimalen Overhead von gleichzeitig Gebäude alle Sprachen Ihrer Website als separaten Prozess. Das bedeutet, Ihre Website Build-Zeit wird nicht davon ab, wie viele Sprachen, die unterstützt werden müssen.
Polyglot ist als eines ruby gem oder als Jekyll Plugin. Es kann mit installiert werden:
gem install 'jekyll-polyglot'
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hallo und willkommen zu einer Beispielseite
Bitte genießen Sie Ihren Aufenthalt
Dieser Beispieltext stammte aus einer .yml Datei
HTML-Tags werden beibehalten
und Links werden relativiert
If you have installed the jekyll-polyglot gem, these additions to your site header can easily provide your jekyll blog with Google-powered SEO bonuses.
Per W3C Internationalization Best Practices you can set the default language of every page with a meta tag. Just add the following to your header:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">You can easily add hreflang alternate tags to your site, achieving SEO with google multi-language searches. Add the following to your header:
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}You can get all of the above with a single tag added to your header.html:
{% I18n_Headers https://untra.github.com/polyglot %}Just add the permanent url for your website and all of the above SEO will be added to each page in your website. In version >= 1.2.4, you can leave it empty, just calling
{% I18n_Headers %}and it will default to your site.url
With this SEO, each page click for one sites language will count towards the net clicks of all languages on the website.
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Después de meses de trabajo y el refinamiento, me siento orgulloso de presentar Polyglot: un plugin para i18n Jekyll sitios que necesidad para atender su contenido a varios idiomas y audiencias.
Si bien hay otros plugins multi-idioma para Jekyll, Polyglot es especial. Polyglot se encarga de las tonterías típicas normalmente de izquierda a los desarrolladores para gestionar (como discusiones urls y la garantía de mapas de sitio consistentes) mientras que proporciona herramientas eficaces y sencillas desarrolladores Jekyll puede utilizar en SEO y agregación de contenidos vía rápida.
En el pasado, un sitio estático multilenguaje blog o tenían que mantener un registro de lo delicado lenguaje cada enlace relativa sitio estaba sirviendo. Era demasiado fácil para un desarrollador para tropezar, y los visitantes de lengua extranjera de forma rápida se perdiera en el contenido sin traducir.
Polyglot relativiza automáticamente las direcciones url para cada idioma que desea su sitio a construir para. Esto permite que los visitantes del sitio para quedarse aislado en un idioma mientras navega por su sitio web.
Cuando usted no se han traducido o contenido multilingüe, Jekyll todavía construir con el contenido que tienen. Cuando usted ha traducido o contenido multilingüe, Jekyll construirá usando ese contenido. Simple como eso.
Sitemaps mantenerse coherente en todos los idiomas, y se traducen estancias en el sitio que fue construido para.
Idioma de los contenidos Rich es normalmente difícil de implementar. Cadenas cortas o lenguaje banderas dependientes suelen ser difícil para un sitio web Jekyll para mantener constante.
Excepto cuando es tan fácil. En su config.yml, simplemente almacenar sus cadenas como:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!y en su liquid, simplemente llame a:
{{ site.hello[site.active_lang]}}produce:
Polyglot va a construir su sitio web en varios idiomas tan rápido como se va a construir su sitio web idioma predeterminado. Polyglot se ejecuta con una sobrecarga mínima de simultáneamente edificio todos los idiomas de su sitio web como proceso independiente. Esto significa que su sitio web el tiempo de construcción no va a ser una función de la cantidad de idiomas que necesita para apoyar.
Polyglot está disponible como una ruby gem, o como un plugin Jekyll. Se puede instalar con:
gem install 'jekyll-polyglot'
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'Una nueva versión de Políglota ha sido puesto en libertad! ¡Darle una oportunidad!
gem install jekyll-polygloty la lista de Jekyll-polyglot entre sus gemas que aparecen en su _config.yml
Se trata en su mayoría bases para prepararse para nuevas características y una mejor gestión de contenidos multilingües. Se tiene una nueva característica:
Ponga esta etiqueta con la URL de su sitio web en su head.html incluye archivos para obtener el máximo previsto por SEO tener un sitio web multilingüe. Es el mismo que el siguiente código de líquido:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}En su cabecera, pero más rápido y más limpio! Para obtener más información, ver la página
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
¡Se ha lanzado una nueva versión de Polyglot! ¡Darle una oportunidad!
gem install jekyll-polyglotEsta versión fue posible gracias al soporte de los siguientes usuarios de github:
site.dataEl contenido específico del idioma definido en el directorio site.data ahora se fusionará recursivamente, de modo que active_lang contenido tiene prioridad sobre default_lang contenido, tiene prioridad sobre sin contenido de idioma. (#59)
default_lang raíz del sitioSi default_lang no está definido en languages, esto garantiza que los archivos de idioma sin asignar (como aquellos excluidos de la localización) se escriban todavía en la raíz del sitio. (#65)
i18n_headers tagEl procesamiento de documentos es ahora más rápido y se realizaron correcciones en el i18n_headers cuando se define el site.url. (#67)
active_lang carga del sitioEsto permite que las claves personalizadas se definan con el active_lang, dando interoperabilidad entre polyglot y otros plugins y themes (#68)
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothref estático no relativizadoEsta versión proporciona una nueva liquid block tag {% static_href %}href=”…”{% endstatic_href %} que se puede utilizar para crear href attributes in anchor tags que no están relativizados por Polyglot.
Jekyll-Polyglot es bastante codicioso e ingenuo en su relativización, por lo que si desea una URL que sea implícitamente estática (como para hacer un cambiador de idioma, por cierto), esta liquid tag will Ayudarte a construir ese desenredado href=”…” tag in anchor elements.
Polyglot 1.4.0 agrega soporte para lang-exclusive: [ ] frontmatter en documentos. Si se agrega a un documento, este frontmatter limitará la generación del documento a ese idioma específico.
---
lang-exclusive: ['es']
---Esta es una forma de controlar qué idiomas pueden ver un documento, incluso si ese documento puede no tener un equivalente en el sitio de idioma predeterminado.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
Je recherche des volontaires qui aimeraient voir le Jekyll-Polyglot homepage representado en su idioma de origen! Si encuentra útil este software y desea ver su idioma representado, simplemente comuníquese con el github issues.
Lanzamiento de parche adicional de Polyglot version 1.4.1 ya disponible!
Fallout from cleanup led to a small fix and some tests.
¡Se han agregado páginas del sitio en idioma ruso!
Je recherche des volontaires qui aimeraient voir le Jekyll-Polyglot homepage representado en su idioma de origen! Si encuentra útil este software y desea ver su idioma representado, simplemente comuníquese con el github issues.
Presentación de Polyglot para la versión version 1.5.0, con nuevo soporte para compilaciones escalonadas por CPU lógico.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
¿Polyglot ha ayudado a que su sitio web se expanda a nuevos territorios y mercados? ¿Tiene alguna sugerencia, contribución o corrección de errores que le gustaría proporcionar? ¿Quiere ver este sitio web traducido a su idioma nativo?
Drop me a line, open a issues or make a PR!
Se agradece mucho todo el apoyo y las contribuciones.
Este enlace permanente es muy largo y complejo
Presentación de Polyglot para la versión version 1.5.0, con nuevo soporte para compilaciones escalonadas por CPU lógico.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
¿Polyglot ha ayudado a que su sitio web se expanda a nuevos territorios y mercados? ¿Tiene alguna sugerencia, contribución o corrección de errores que le gustaría proporcionar? ¿Quiere ver este sitio web traducido a su idioma nativo?
Drop me a line, open a issues or make a PR!
Se agradece mucho todo el apoyo y las contribuciones.
Lanzamiento de parche adicional de Polyglot version 1.4.1 ya disponible!
Fallout from cleanup led to a small fix and some tests.
¡Se han agregado páginas del sitio en idioma ruso!
Je recherche des volontaires qui aimeraient voir le Jekyll-Polyglot homepage representado en su idioma de origen! Si encuentra útil este software y desea ver su idioma representado, simplemente comuníquese con el github issues.
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothref estático no relativizadoEsta versión proporciona una nueva liquid block tag {% static_href %}href=”…”{% endstatic_href %} que se puede utilizar para crear href attributes in anchor tags que no están relativizados por Polyglot.
Jekyll-Polyglot es bastante codicioso e ingenuo en su relativización, por lo que si desea una URL que sea implícitamente estática (como para hacer un cambiador de idioma, por cierto), esta liquid tag will Ayudarte a construir ese desenredado href=”…” tag in anchor elements.
Polyglot 1.4.0 agrega soporte para lang-exclusive: [ ] frontmatter en documentos. Si se agrega a un documento, este frontmatter limitará la generación del documento a ese idioma específico.
---
lang-exclusive: ['es']
---Esta es una forma de controlar qué idiomas pueden ver un documento, incluso si ese documento puede no tener un equivalente en el sitio de idioma predeterminado.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
Je recherche des volontaires qui aimeraient voir le Jekyll-Polyglot homepage representado en su idioma de origen! Si encuentra útil este software y desea ver su idioma representado, simplemente comuníquese con el github issues.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
¡Se ha lanzado una nueva versión de Polyglot! ¡Darle una oportunidad!
gem install jekyll-polyglotEsta versión fue posible gracias al soporte de los siguientes usuarios de github:
site.dataEl contenido específico del idioma definido en el directorio site.data ahora se fusionará recursivamente, de modo que active_lang contenido tiene prioridad sobre default_lang contenido, tiene prioridad sobre sin contenido de idioma. (#59)
default_lang raíz del sitioSi default_lang no está definido en languages, esto garantiza que los archivos de idioma sin asignar (como aquellos excluidos de la localización) se escriban todavía en la raíz del sitio. (#65)
i18n_headers tagEl procesamiento de documentos es ahora más rápido y se realizaron correcciones en el i18n_headers cuando se define el site.url. (#67)
active_lang carga del sitioEsto permite que las claves personalizadas se definan con el active_lang, dando interoperabilidad entre polyglot y otros plugins y themes (#68)
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
Una nueva versión de Políglota ha sido puesto en libertad! ¡Darle una oportunidad!
gem install jekyll-polygloty la lista de Jekyll-polyglot entre sus gemas que aparecen en su _config.yml
Se trata en su mayoría bases para prepararse para nuevas características y una mejor gestión de contenidos multilingües. Se tiene una nueva característica:
Ponga esta etiqueta con la URL de su sitio web en su head.html incluye archivos para obtener el máximo previsto por SEO tener un sitio web multilingüe. Es el mismo que el siguiente código de líquido:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}En su cabecera, pero más rápido y más limpio! Para obtener más información, ver la página
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'Después de meses de trabajo y el refinamiento, me siento orgulloso de presentar Polyglot: un plugin para i18n Jekyll sitios que necesidad para atender su contenido a varios idiomas y audiencias.
Si bien hay otros plugins multi-idioma para Jekyll, Polyglot es especial. Polyglot se encarga de las tonterías típicas normalmente de izquierda a los desarrolladores para gestionar (como discusiones urls y la garantía de mapas de sitio consistentes) mientras que proporciona herramientas eficaces y sencillas desarrolladores Jekyll puede utilizar en SEO y agregación de contenidos vía rápida.
En el pasado, un sitio estático multilenguaje blog o tenían que mantener un registro de lo delicado lenguaje cada enlace relativa sitio estaba sirviendo. Era demasiado fácil para un desarrollador para tropezar, y los visitantes de lengua extranjera de forma rápida se perdiera en el contenido sin traducir.
Polyglot relativiza automáticamente las direcciones url para cada idioma que desea su sitio a construir para. Esto permite que los visitantes del sitio para quedarse aislado en un idioma mientras navega por su sitio web.
Cuando usted no se han traducido o contenido multilingüe, Jekyll todavía construir con el contenido que tienen. Cuando usted ha traducido o contenido multilingüe, Jekyll construirá usando ese contenido. Simple como eso.
Sitemaps mantenerse coherente en todos los idiomas, y se traducen estancias en el sitio que fue construido para.
Idioma de los contenidos Rich es normalmente difícil de implementar. Cadenas cortas o lenguaje banderas dependientes suelen ser difícil para un sitio web Jekyll para mantener constante.
Excepto cuando es tan fácil. En su config.yml, simplemente almacenar sus cadenas como:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!y en su liquid, simplemente llame a:
{{ site.hello[site.active_lang]}}produce:
Polyglot va a construir su sitio web en varios idiomas tan rápido como se va a construir su sitio web idioma predeterminado. Polyglot se ejecuta con una sobrecarga mínima de simultáneamente edificio todos los idiomas de su sitio web como proceso independiente. Esto significa que su sitio web el tiempo de construcción no va a ser una función de la cantidad de idiomas que necesita para apoyar.
Polyglot está disponible como una ruby gem, o como un plugin Jekyll. Se puede instalar con:
gem install 'jekyll-polyglot'
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hola , y bienvenidos a una página de ejemplo
disfrutar de su estancia por favor
Este texto de muestra proviene de un archivo .yml en el directorio _data
etiquetas HTML se conservan
y los enlaces se relativizan
If you have installed the jekyll-polyglot gem, these additions to your site header can easily provide your jekyll blog with Google-powered SEO bonuses.
Per W3C Internationalization Best Practices you can set the default language of every page with a meta tag. Just add the following to your header:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">You can easily add hreflang alternate tags to your site, achieving SEO with google multi-language searches. Add the following to your header:
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}You can get all of the above with a single tag added to your header.html:
{% I18n_Headers https://untra.github.com/polyglot %}Just add the permanent url for your website and all of the above SEO will be added to each page in your website. In version >= 1.2.4, you can leave it empty, just calling
{% I18n_Headers %}and it will default to your site.url
With this SEO, each page click for one sites language will count towards the net clicks of all languages on the website.
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Après des mois de travail et de raffinement, je suis fier de présenter Polyglot: un plugin i18n pour Jekyll sites qui besoin pour répondre à leur contenu à de multiples langues et le public.
Bien qu’il existe d’autres plugins multi-langues pour Jekyll, Polyglot est spécial. Polyglot prend soin de l’absurdité typique normalement laissée aux développeurs de gérer (comme querelles urls et assurer sitemaps cohérentes) tout en fournissant des outils simples et efficaces développeurs Jekyll peut utiliser dans le référencement et l’agrégation de contenu accéléré.
Dans le passé, un site ou un blog statique multi-langue devaient garder une trace délicate que soit la langue de chaque lien relatif le site servait. Il était trop facile pour un développeur de trébucher, et les visiteurs de langue étrangère serait rapidement se perdre dans le contenu non traduite.
Polyglot relativise automatiquement les Url pour chaque langue que vous voulez que votre site pour construire. Cela permet les visiteurs du site à rester isolé sur une langue tout en naviguant sur votre site web.
Lorsque vous ne ont traduit ou contenu multilingue, Jekyll aurez toujours construire avec le contenu que vous avez. Lorsque vous ne avez traduit ou contenu multilingue, Jekyll se construire en utilisant ce contenu. Aussi simple que cela.
Sitemaps rester cohérente dans toutes les langues, et traduits séjours dans le site, il a été construit pour.
Un contenu riche de la langue est normalement difficile à mettre en œuvre. Les chaînes courtes ou des bannières dépendant de la langue sont généralement difficile pour un site Jekyll pour garder cohérente.
Sauf quand il est si facile. Dans votre config.yml, simplement stocker vos chaînes comme:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!et dans votre liquid, il suffit d’appeler:
{{ site.hello[site.active_lang]}}produit:
Polyglot va construire votre site multi-langue aussi vite que il va construire votre site de langue par défaut. Polyglot fonctionne avec un minimum de frais généraux par simultanément bâtiment toutes les langues de votre site Web comme un processus distinct. Cela signifie que votre temps site de construction ne sera pas fonction du nombre de langues dont vous avez besoin pour soutenir.
Polyglot est disponible comme une ruby gem, ou comme un plugin Jekyll. Il peut être installé avec:
gem install 'jekyll-polyglot'
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'Une nouvelle version de Polyglot a été libéré! Essaie!
gem install jekyll-polyglotet la liste jekyll-polyglot parmi vos pierres précieuses figurant dans votre _config.yml
Elle consiste principalement bases pour se préparer à de nouvelles fonctionnalités et une meilleure gestion de contenu multilingue. Elle a une nouvelle fonctionnalité:
Mettez cette balise avec le url de votre site dans votre head.html comprend fichier pour obtenir le référencement maximum fourni par ayant un site Web multilingue. Il est le même que le code de liquide suivant:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}Dans votre tête, mais plus rapide et plus propre! Pour plus d’informations, voir la page SEO
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
Une nouvelle version de Polyglot a été lancée! Essaie!
gem install jekyll-polyglotCette version a été rendue possible avec le soutien des utilisateurs suivants de github:
site.dataLe contenu spécifique au langage défini dans votre répertoire site.data sera désormais fusionné récursivement, de sorte que active_lang contenu obtient la priorité sur default_lang contenu, obtient la priorité sur aucun contenu de langue. (#59)
default_lang la racine du siteSi le default_lang n’est pas défini dans les languages, cela garantit que les fichiers non assignés aux langues (tels que ceux exclus de la localisation) sont toujours écrits sur la racine du site. (#65)
i18n_headers tagLe traitement des documents est maintenant plus rapide, et des correctifs ont été effectués sur i18n_headers pour quand le site.url est défini. (#67)
active_lang charge du siteCela permet de définir des clés personnalisées avec active_lang, ce qui donne une interopérabilité entre les polyglottes et d’autres plugins et thèmes. (#68)
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefCette version fournit un nouveau liquid block tag {% static_href %}href=”…”{% endstatic_href %} qui peut être utilisé pour créer href attributes in anchor tags qui ne sont pas relativisés par Polyglot.
Jekyll-Polyglot est assez gourmand et naïf dans sa relativisation, et donc si vous voulez une url implicitement statique (comme pour faire un sélecteur de langue, au fait), ce liquid tag will vous aider à construire ce démêlé href=”…” tag in anchor elements.
Polyglot 1.4.0 ajoute le support pour lang-exclusive: [ ] frontmatter dans les documents. S’il est ajouté à un document, ce frontmatter limitera la génération du document à cette langue spécifique.
---
lang-exclusive: ['fr']
---C’est un moyen de contrôler quelles langues peuvent voir un document, même si ce document n’a pas d’équivalent dans le site de langue par défaut.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
Je recherche des volontaires qui aimeraient voir le Jekyll-Polyglot homepage représenté dans votre langue d’origine! Si vous trouvez ce logiciel utile et que vous souhaitez voir votre langue représentée, contactez simplement le github issues.
Bonus patch release of Polyglot version 1.4.1 is out!
Fallout from cleanup led to a small fix and some tests
Russian language site pages have been added!
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Version polyglotte pour la version version 1.5.0, avec une nouvelle prise en charge des builds échelonnés par processeur logique.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Polyglot a-t-il aidé votre site Web à se développer sur de nouveaux territoires et marchés ? Avez-vous une suggestion, une contribution ou une correction de bogue que vous aimeriez fournir ? Vous voulez voir ce site Web traduit dans votre langue maternelle ?
Drop me a line, open a issues or make a PR!
Tout le soutien et les contributions sont grandement appréciés.
Ce permalien est vraiment long et complexe
Version polyglotte pour la version version 1.5.0, avec une nouvelle prise en charge des builds échelonnés par processeur logique.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Polyglot a-t-il aidé votre site Web à se développer sur de nouveaux territoires et marchés ? Avez-vous une suggestion, une contribution ou une correction de bogue que vous aimeriez fournir ? Vous voulez voir ce site Web traduit dans votre langue maternelle ?
Drop me a line, open a issues or make a PR!
Tout le soutien et les contributions sont grandement appréciés.
Bonus patch release of Polyglot version 1.4.1 is out!
Fallout from cleanup led to a small fix and some tests
Russian language site pages have been added!
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefCette version fournit un nouveau liquid block tag {% static_href %}href=”…”{% endstatic_href %} qui peut être utilisé pour créer href attributes in anchor tags qui ne sont pas relativisés par Polyglot.
Jekyll-Polyglot est assez gourmand et naïf dans sa relativisation, et donc si vous voulez une url implicitement statique (comme pour faire un sélecteur de langue, au fait), ce liquid tag will vous aider à construire ce démêlé href=”…” tag in anchor elements.
Polyglot 1.4.0 ajoute le support pour lang-exclusive: [ ] frontmatter dans les documents. S’il est ajouté à un document, ce frontmatter limitera la génération du document à cette langue spécifique.
---
lang-exclusive: ['fr']
---C’est un moyen de contrôler quelles langues peuvent voir un document, même si ce document n’a pas d’équivalent dans le site de langue par défaut.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
Je recherche des volontaires qui aimeraient voir le Jekyll-Polyglot homepage représenté dans votre langue d’origine! Si vous trouvez ce logiciel utile et que vous souhaitez voir votre langue représentée, contactez simplement le github issues.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
Une nouvelle version de Polyglot a été lancée! Essaie!
gem install jekyll-polyglotCette version a été rendue possible avec le soutien des utilisateurs suivants de github:
site.dataLe contenu spécifique au langage défini dans votre répertoire site.data sera désormais fusionné récursivement, de sorte que active_lang contenu obtient la priorité sur default_lang contenu, obtient la priorité sur aucun contenu de langue. (#59)
default_lang la racine du siteSi le default_lang n’est pas défini dans les languages, cela garantit que les fichiers non assignés aux langues (tels que ceux exclus de la localisation) sont toujours écrits sur la racine du site. (#65)
i18n_headers tagLe traitement des documents est maintenant plus rapide, et des correctifs ont été effectués sur i18n_headers pour quand le site.url est défini. (#67)
active_lang charge du siteCela permet de définir des clés personnalisées avec active_lang, ce qui donne une interopérabilité entre les polyglottes et d’autres plugins et thèmes. (#68)
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
Une nouvelle version de Polyglot a été libéré! Essaie!
gem install jekyll-polyglotet la liste jekyll-polyglot parmi vos pierres précieuses figurant dans votre _config.yml
Elle consiste principalement bases pour se préparer à de nouvelles fonctionnalités et une meilleure gestion de contenu multilingue. Elle a une nouvelle fonctionnalité:
Mettez cette balise avec le url de votre site dans votre head.html comprend fichier pour obtenir le référencement maximum fourni par ayant un site Web multilingue. Il est le même que le code de liquide suivant:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}Dans votre tête, mais plus rapide et plus propre! Pour plus d’informations, voir la page SEO
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'Après des mois de travail et de raffinement, je suis fier de présenter Polyglot: un plugin i18n pour Jekyll sites qui besoin pour répondre à leur contenu à de multiples langues et le public.
Bien qu’il existe d’autres plugins multi-langues pour Jekyll, Polyglot est spécial. Polyglot prend soin de l’absurdité typique normalement laissée aux développeurs de gérer (comme querelles urls et assurer sitemaps cohérentes) tout en fournissant des outils simples et efficaces développeurs Jekyll peut utiliser dans le référencement et l’agrégation de contenu accéléré.
Dans le passé, un site ou un blog statique multi-langue devaient garder une trace délicate que soit la langue de chaque lien relatif le site servait. Il était trop facile pour un développeur de trébucher, et les visiteurs de langue étrangère serait rapidement se perdre dans le contenu non traduite.
Polyglot relativise automatiquement les Url pour chaque langue que vous voulez que votre site pour construire. Cela permet les visiteurs du site à rester isolé sur une langue tout en naviguant sur votre site web.
Lorsque vous ne ont traduit ou contenu multilingue, Jekyll aurez toujours construire avec le contenu que vous avez. Lorsque vous ne avez traduit ou contenu multilingue, Jekyll se construire en utilisant ce contenu. Aussi simple que cela.
Sitemaps rester cohérente dans toutes les langues, et traduits séjours dans le site, il a été construit pour.
Un contenu riche de la langue est normalement difficile à mettre en œuvre. Les chaînes courtes ou des bannières dépendant de la langue sont généralement difficile pour un site Jekyll pour garder cohérente.
Sauf quand il est si facile. Dans votre config.yml, simplement stocker vos chaînes comme:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!et dans votre liquid, il suffit d’appeler:
{{ site.hello[site.active_lang]}}produit:
Polyglot va construire votre site multi-langue aussi vite que il va construire votre site de langue par défaut. Polyglot fonctionne avec un minimum de frais généraux par simultanément bâtiment toutes les langues de votre site Web comme un processus distinct. Cela signifie que votre temps site de construction ne sera pas fonction du nombre de langues dont vous avez besoin pour soutenir.
Polyglot est disponible comme une ruby gem, ou comme un plugin Jekyll. Il peut être installé avec:
gem install 'jekyll-polyglot'
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
bonjour, et bienvenue à une page d’exemple
s’il vous plaît profiter de votre séjour
Cet exemple de texte provient d’un fichier .yml dans le répertoire _data
balises html sont conservées
et les liens sont relativisées
If you have installed the jekyll-polyglot gem, these additions to your site header can easily provide your jekyll blog with Google-powered SEO bonuses.
Per W3C Internationalization Best Practices you can set the default language of every page with a meta tag. Just add the following to your header:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">You can easily add hreflang alternate tags to your site, achieving SEO with google multi-language searches. Add the following to your header:
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}You can get all of the above with a single tag added to your header.html:
{% I18n_Headers https://untra.github.com/polyglot %}Just add the permanent url for your website and all of the above SEO will be added to each page in your website. In version >= 1.2.4, you can leave it empty, just calling
{% I18n_Headers %}and it will default to your site.url
With this SEO, each page click for one sites language will count towards the net clicks of all languages on the website.
Polyglot Release for version version 1.5.0, with new support for staggered builds by logical cpus.
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Has Polyglot helped your website expand into new territories and markets? Do you have a suggestion, contribution or bugfix you’d like to provide? Want to see this website translated into your native language?
Drop me a line, open a issues or make a PR! All support and contributions are greatly appreciated.
Bonus patch release of Polyglot version 1.4.1 is out!
Fallout from cleanup led to a small fix and some tests
Russian language site pages have been added!
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefThis release provides a new liquid block tag {% static_href %}href=”…”{% endstatic_href %} which can be used to create href attributes in anchor tags that are not relativized by Polyglot.
Jekyll-Polyglot is fairly greedy and naive in it’s relativization, and so if you want a url that is explicitly static (such as for making a language switcher, hint hint), this liquid tag will help you construct that unmangled href=”…” tag in anchor elements.
Polyglot 1.4.0 adds support for lang-exclusive: [ ] frontmatter in documents. If added to a document, this frontmatter will limit generation of the document to that specific language.
---
lang-exclusive: ['en']
---This is a way to control which languages may see a document, even if that document may not have an equivalent in the default language site.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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!
gem install jekyll-polyglotThis release was made possible with the support of the following github users:
site.dataLanguage 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!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotand 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:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}In your header, but faster and cleaner! For more information, see the SEO page
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'After months of work and refinement, I am proud to present Polyglot: a i18n plugin for Jekyll sites that need to cater their content to multiple languages and audiences.
While there are other multi-language plugins for Jekyll, Polyglot is special. Polyglot takes care of the typical cruftwork normally left to developers to manage (such as wrangling urls and ensuring consistent sitemaps) while providing efficient and simple tools Jekyll developers can utilize into SEO and fast-tracked content aggregation.
In the past, a multi-language static site or blog had to keep delicate track of what language each relative link the site was serving. It was all too easy for a developer to stumble, and foreign language visitors would quickly get lost in untranslated content.
Polyglot automatically relativizes the urls for each language you want your site to build for. This allows website visitors to stay isolated on one language while browsing your website.
When you don’t have translated or multilingual content, Jekyll will still build with the content you do have. When you do have translated or multilingual content, Jekyll will build using that content. Simple as that.
Sitemaps stay consistent across all languages, and translated stays in the site it was built for.
Rich language content is normally hard to implement. Short strings or language dependent banners are typically hard for a Jekyll website to keep consistent.
Except when it’s this easy. In your config.yml, just store your strings as:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!and in your liquid, just call:
{{ site.hello[site.active_lang]}}produces:
Polyglot will build your multi-language website just as fast as it will build your default language website. Polyglot runs with a minimal overhead by simultaneously building all languages of your website as separate process. This means your website build time won’t be a function of how many languages you need to support.
Polyglot is available as a gem, or as a Jekyll plugin. It can be installed with:
gem install 'jekyll-polyglot'
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
`, * or to a parent if there are multiple elements to show. */ .message { margin-bottom: 1rem; padding: 1rem; color: #717171; background-color: #f9f9f9; } /* * Container * * Center the page content. */ .container { max-width: 42rem; padding-left: 1rem; padding-right: 1rem; margin-left: auto; margin-right: auto; } /* * Masthead * * Super small header above the content for site name and short description. */ .masthead { padding-top: 1rem; padding-bottom: 1rem; margin-bottom: 3rem; } .masthead-title { margin-top: 0; margin-bottom: 0; color: #505050; } .masthead-title a { color: #505050; } .masthead-title small { font-size: 75%; font-weight: 400; color: #c0c0c0; letter-spacing: 0; } /* * Posts and pages * * Each post is wrapped in `.post` and is used on default and post layouts. Each * page is wrapped in `.page` and is only used on the page layout. */ .page, .post { margin-bottom: 4em; } /* Blog post or page title */ .page-title, .post-title, .post-title a { color: #303030; } .page-title, .post-title { margin-top: 0; } /* Meta data line below post title */ .post-date { display: block; margin-top: -.5rem; margin-bottom: 1rem; color: #9a9a9a; } /* Related posts */ .related { padding-top: 2rem; padding-bottom: 2rem; border-top: 1px solid #eee; } .related-posts { padding-left: 0; list-style: none; } .related-posts h3 { margin-top: 0; } .related-posts li small { font-size: 75%; color: #999; } .related-posts li a:hover { color: #268bd2; text-decoration: none; } .related-posts li a:hover small { color: inherit; } /* * Pagination * * Super lightweight (HTML-wise) blog pagination. `span`s are provide for when * there are no more previous or next posts to show. */ .pagination { overflow: hidden; /* clearfix */ margin-left: -1rem; margin-right: -1rem; font-family: "PT Sans", Helvetica, Arial, sans-serif; color: #ccc; text-align: center; } /* Pagination items can be `span`s or `a`s */ .pagination-item { display: block; padding: 1rem; border: 1px solid #eee; } .pagination-item:first-child { margin-bottom: -1px; } /* Only provide a hover state for linked pagination items */ a.pagination-item:hover { background-color: #f5f5f5; } @media (min-width: 30em) { .pagination { margin: 3rem 0; } .pagination-item { float: left; width: 50%; } .pagination-item:first-child { margin-bottom: 0; border-top-left-radius: 4px; border-bottom-left-radius: 4px; } .pagination-item:last-child { margin-left: -1px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; } } polyglot-1.5.0/site/_site/public/css/syntax.css 0000664 0000000 0000000 00000006627 14074562261 0021565 0 ustar 00root root 0000000 0000000 .highlight .hll { background-color: #ffc; } .highlight .c { color: #999; } /* Comment */ .highlight .err { color: #a00; background-color: #faa } /* Error */ .highlight .k { color: #069; } /* Keyword */ .highlight .o { color: #555 } /* Operator */ .highlight .cm { color: #09f; font-style: italic } /* Comment.Multiline */ .highlight .cp { color: #099 } /* Comment.Preproc */ .highlight .c1 { color: #999; } /* Comment.Single */ .highlight .cs { color: #999; } /* Comment.Special */ .highlight .gd { background-color: #fcc; border: 1px solid #c00 } /* Generic.Deleted */ .highlight .ge { font-style: italic } /* Generic.Emph */ .highlight .gr { color: #f00 } /* Generic.Error */ .highlight .gh { color: #030; } /* Generic.Heading */ .highlight .gi { background-color: #cfc; border: 1px solid #0c0 } /* Generic.Inserted */ .highlight .go { color: #aaa } /* Generic.Output */ .highlight .gp { color: #009; } /* Generic.Prompt */ .highlight .gs { } /* Generic.Strong */ .highlight .gu { color: #030; } /* Generic.Subheading */ .highlight .gt { color: #9c6 } /* Generic.Traceback */ .highlight .kc { color: #069; } /* Keyword.Constant */ .highlight .kd { color: #069; } /* Keyword.Declaration */ .highlight .kn { color: #069; } /* Keyword.Namespace */ .highlight .kp { color: #069 } /* Keyword.Pseudo */ .highlight .kr { color: #069; } /* Keyword.Reserved */ .highlight .kt { color: #078; } /* Keyword.Type */ .highlight .m { color: #f60 } /* Literal.Number */ .highlight .s { color: #d44950 } /* Literal.String */ .highlight .na { color: #4f9fcf } /* Name.Attribute */ .highlight .nb { color: #366 } /* Name.Builtin */ .highlight .nc { color: #0a8; } /* Name.Class */ .highlight .no { color: #360 } /* Name.Constant */ .highlight .nd { color: #99f } /* Name.Decorator */ .highlight .ni { color: #999; } /* Name.Entity */ .highlight .ne { color: #c00; } /* Name.Exception */ .highlight .nf { color: #c0f } /* Name.Function */ .highlight .nl { color: #99f } /* Name.Label */ .highlight .nn { color: #0cf; } /* Name.Namespace */ .highlight .nt { color: #2f6f9f; } /* Name.Tag */ .highlight .nv { color: #033 } /* Name.Variable */ .highlight .ow { color: #000; } /* Operator.Word */ .highlight .w { color: #bbb } /* Text.Whitespace */ .highlight .mf { color: #f60 } /* Literal.Number.Float */ .highlight .mh { color: #f60 } /* Literal.Number.Hex */ .highlight .mi { color: #f60 } /* Literal.Number.Integer */ .highlight .mo { color: #f60 } /* Literal.Number.Oct */ .highlight .sb { color: #c30 } /* Literal.String.Backtick */ .highlight .sc { color: #c30 } /* Literal.String.Char */ .highlight .sd { color: #c30; font-style: italic } /* Literal.String.Doc */ .highlight .s2 { color: #c30 } /* Literal.String.Double */ .highlight .se { color: #c30; } /* Literal.String.Escape */ .highlight .sh { color: #c30 } /* Literal.String.Heredoc */ .highlight .si { color: #a00 } /* Literal.String.Interpol */ .highlight .sx { color: #c30 } /* Literal.String.Other */ .highlight .sr { color: #3aa } /* Literal.String.Regex */ .highlight .s1 { color: #c30 } /* Literal.String.Single */ .highlight .ss { color: #fc3 } /* Literal.String.Symbol */ .highlight .bp { color: #366 } /* Name.Builtin.Pseudo */ .highlight .vc { color: #033 } /* Name.Variable.Class */ .highlight .vg { color: #033 } /* Name.Variable.Global */ .highlight .vi { color: #033 } /* Name.Variable.Instance */ .highlight .il { color: #f60 } /* Literal.Number.Integer.Long */ .css .o, .css .o + .nt, .css .nt + .nt { color: #999; } polyglot-1.5.0/site/_site/public/favicon.ico 0000664 0000000 0000000 00000000473 14074562261 0021047 0 ustar 00root root 0000000 0000000 PNG IHDR pHYs H H Fk> vpAg IDATHcTRTd%` X0f͘)~pޤT'{x{c*8zP\B>`d$ |p=d Hy`Ԃ` 6`>`dZh$x+WBسf`úuDY{ny9w ?z)8ڲb 69 "zTXtSoftware xsLOJUMLO JML /Ԯ M IENDB` polyglot-1.5.0/site/_site/ru/ 0000775 0000000 0000000 00000000000 14074562261 0016072 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/site/_site/ru/2012/ 0000775 0000000 0000000 00000000000 14074562261 0016456 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/site/_site/ru/2012/02/ 0000775 0000000 0000000 00000000000 14074562261 0016677 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/site/_site/ru/2012/02/06/ 0000775 0000000 0000000 00000000000 14074562261 0017124 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/site/_site/ru/2012/02/06/whats-jekyll/ 0000775 0000000 0000000 00000000000 14074562261 0021542 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/site/_site/ru/2012/02/06/whats-jekyll/index.html 0000664 0000000 0000000 00000014107 14074562261 0023542 0 ustar 00root root 0000000 0000000
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
After months of work and refinement, I am proud to present Polyglot: a i18n plugin for Jekyll sites that need to cater their content to multiple languages and audiences.
While there are other multi-language plugins for Jekyll, Polyglot is special. Polyglot takes care of the typical cruftwork normally left to developers to manage (such as wrangling urls and ensuring consistent sitemaps) while providing efficient and simple tools Jekyll developers can utilize into SEO and fast-tracked content aggregation.
In the past, a multi-language static site or blog had to keep delicate track of what language each relative link the site was serving. It was all too easy for a developer to stumble, and foreign language visitors would quickly get lost in untranslated content.
Polyglot automatically relativizes the urls for each language you want your site to build for. This allows website visitors to stay isolated on one language while browsing your website.
When you don’t have translated or multilingual content, Jekyll will still build with the content you do have. When you do have translated or multilingual content, Jekyll will build using that content. Simple as that.
Sitemaps stay consistent across all languages, and translated stays in the site it was built for.
Rich language content is normally hard to implement. Short strings or language dependent banners are typically hard for a Jekyll website to keep consistent.
Except when it’s this easy. In your config.yml, just store your strings as:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!and in your liquid, just call:
{{ site.hello[site.active_lang]}}produces:
Polyglot will build your multi-language website just as fast as it will build your default language website. Polyglot runs with a minimal overhead by simultaneously building all languages of your website as separate process. This means your website build time won’t be a function of how many languages you need to support.
Polyglot is available as a gem, or as a Jekyll plugin. It can be installed with:
gem install 'jekyll-polyglot'
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotand 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:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}In your header, but faster and cleaner! For more information, see the SEO page
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotThis release was made possible with the support of the following github users:
site.dataLanguage 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)
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefThis release provides a new liquid block tag {% static_href %}href=”…”{% endstatic_href %} which can be used to create href attributes in anchor tags that are not relativized by Polyglot.
Jekyll-Polyglot is fairly greedy and naive in it’s relativization, and so if you want a url that is explicitly static (such as for making a language switcher, hint hint), this liquid tag will help you construct that unmangled href=”…” tag in anchor elements.
Polyglot 1.4.0 adds support for lang-exclusive: [ ] frontmatter in documents. If added to a document, this frontmatter will limit generation of the document to that specific language.
---
lang-exclusive: ['ru']
---This is a way to control which languages may see a document, even if that document may not have an equivalent in the default language site.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
Выпуск бонусного патча Polyglot version 1.4.1 теперь доступно!
Последствия очистки привели к небольшому исправлению и некоторым тестам.
Добавлены русскоязычные страницы сайта! Ура, друзья!
Я ищу добровольцев, которые хотели бы увидеть Jekyll-Polyglot homepage представлены на вашем родном языке! Если вы найдете это программное обеспечение полезным и хотите, чтобы ваш язык был представлен на нем, просто свяжитесь с github issues.
Полиглот Релиз для версии version 1.5.0, с новой поддержкой поэтапной сборки по логическому процессору..
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Помогло ли Polyglot расширить ваш веб-сайт на новые территории и рынки? У вас есть предложения, предложения или исправления, которые вы хотели бы внести? Хотите, чтобы этот веб-сайт был переведен на ваш родной язык?
Drop me a line, open a issues or make a PR!
Мы очень ценим любую поддержку и вклад.
Действительно длинная постоянная ссылка.
Полиглот Релиз для версии version 1.5.0, с новой поддержкой поэтапной сборки по логическому процессору..
This release modifies polyglot to start builds only after it confirms there is a cpu core ready to receive the build thread. This makes jekyll site builds run much faster on machines building more languages than with logical cpus ready to process the builds, preventing machine thrash and streamlining builds for large sites.
This release was made possible with the support of the following github users!
Помогло ли Polyglot расширить ваш веб-сайт на новые территории и рынки? У вас есть предложения, предложения или исправления, которые вы хотели бы внести? Хотите, чтобы этот веб-сайт был переведен на ваш родной язык?
Drop me a line, open a issues or make a PR!
Мы очень ценим любую поддержку и вклад.
Выпуск бонусного патча Polyglot version 1.4.1 теперь доступно!
Последствия очистки привели к небольшому исправлению и некоторым тестам.
Добавлены русскоязычные страницы сайта! Ура, друзья!
Я ищу добровольцев, которые хотели бы увидеть Jekyll-Polyglot homepage представлены на вашем родном языке! Если вы найдете это программное обеспечение полезным и хотите, чтобы ваш язык был представлен на нем, просто свяжитесь с github issues.
Polyglot version 1.4.0 is out!
gem install jekyll-polyglothrefThis release provides a new liquid block tag {% static_href %}href=”…”{% endstatic_href %} which can be used to create href attributes in anchor tags that are not relativized by Polyglot.
Jekyll-Polyglot is fairly greedy and naive in it’s relativization, and so if you want a url that is explicitly static (such as for making a language switcher, hint hint), this liquid tag will help you construct that unmangled href=”…” tag in anchor elements.
Polyglot 1.4.0 adds support for lang-exclusive: [ ] frontmatter in documents. If added to a document, this frontmatter will limit generation of the document to that specific language.
---
lang-exclusive: ['ru']
---This is a way to control which languages may see a document, even if that document may not have an equivalent in the default language site.
The {% static_href %} tag is also available as {% Static_Href %} , and the existing {% I18n_Headers %} tag now can be called as {% i18n_headers %}
I am looking for any volunteers that would like to see the Jekyll-Polyglot homepage represented in your language of origin! If you find this software helpful and want to see your language represented, just reach out on the github issues.
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.
gem install jekyll-polyglotThis release was made possible with the support of the following github user!
Polyglot version 1.3.2 has been released! Give it a try!
gem install jekyll-polyglotThis 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!
gem install jekyll-polyglotThis release was made possible with the support of the following github users:
site.dataLanguage 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!
gem install jekyll-polyglotThis 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:
{{ site.data[site.active_lang].richTextString }}Now rich text can be rendered with just:
{{ site.data.richTextString }}I18n_Headers tag now defaults to site.url when left blankUsers can now use
{% I18n_Headers %}without specifying a url, defaulting it to your site.url
A new version of Polyglot has been released! Give it a try!
gem install jekyll-polyglotand 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:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}In your header, but faster and cleaner! For more information, see the SEO page
Polyglot now fully supports Jekyll 3.0 blogs! Go give it a try!
gem 'jekyll-polyglot', '~> 1.1.0'After months of work and refinement, I am proud to present Polyglot: a i18n plugin for Jekyll sites that need to cater their content to multiple languages and audiences.
While there are other multi-language plugins for Jekyll, Polyglot is special. Polyglot takes care of the typical cruftwork normally left to developers to manage (such as wrangling urls and ensuring consistent sitemaps) while providing efficient and simple tools Jekyll developers can utilize into SEO and fast-tracked content aggregation.
In the past, a multi-language static site or blog had to keep delicate track of what language each relative link the site was serving. It was all too easy for a developer to stumble, and foreign language visitors would quickly get lost in untranslated content.
Polyglot automatically relativizes the urls for each language you want your site to build for. This allows website visitors to stay isolated on one language while browsing your website.
When you don’t have translated or multilingual content, Jekyll will still build with the content you do have. When you do have translated or multilingual content, Jekyll will build using that content. Simple as that.
Sitemaps stay consistent across all languages, and translated stays in the site it was built for.
Rich language content is normally hard to implement. Short strings or language dependent banners are typically hard for a Jekyll website to keep consistent.
Except when it’s this easy. In your config.yml, just store your strings as:
hello:
en: Hello!
es: ¡hola!
fr: Bonjour!
de: Guten Tag!and in your liquid, just call:
{{ site.hello[site.active_lang]}}produces:
Polyglot will build your multi-language website just as fast as it will build your default language website. Polyglot runs with a minimal overhead by simultaneously building all languages of your website as separate process. This means your website build time won’t be a function of how many languages you need to support.
Polyglot is available as a gem, or as a Jekyll plugin. It can be installed with:
gem install 'jekyll-polyglot'
Hyde is a brazen two-column Jekyll theme that pairs a prominent sidebar with uncomplicated content. It’s based on Poole, the Jekyll butler.
Poole is the Jekyll Butler, serving as an upstanding and effective foundation for Jekyll themes by @mdo. Poole, and every theme built on it (like Hyde here) includes the following:
rem units in the CSSIn addition to the features of Poole, Hyde adds the following:
<body> classes<body> classesHead to the readme to learn more.
Hyde is by preference a forward-thinking project. In addition to the latest versions of Chrome, Safari (mobile and desktop), and Firefox, it is only compatible with Internet Explorer 9 and above.
Hyde is developed on and hosted with GitHub. Head to the GitHub repository for downloads, bug reports, and features requests.
Thanks!
Jekyll is a static site generator, an open-source tool for creating simple yet powerful websites of all shapes and sizes. From the project’s readme:
Jekyll is a simple, blog aware, static site generator. It takes a template directory […] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
It’s an immensely useful tool and one we encourage you to use here with Hyde.
Find out more by visiting the project on GitHub.
привет и добро пожаловать на образец страницы
пожалуйста, наслаждайтесь вашим пребыванием
Этот образец текста взят из файла .yml в каталоге _data.
HTML-теги сохранился
и ссылки релятивизированный
If you have installed the jekyll-polyglot gem, these additions to your site header can easily provide your jekyll blog with Google-powered SEO bonuses.
Per W3C Internationalization Best Practices you can set the default language of every page with a meta tag. Just add the following to your header:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">You can easily add hreflang alternate tags to your site, achieving SEO with google multi-language searches. Add the following to your header:
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}You can get all of the above with a single tag added to your header.html:
{% I18n_Headers https://untra.github.com/polyglot %}Just add the permanent url for your website and all of the above SEO will be added to each page in your website. In version >= 1.2.4, you can leave it empty, just calling
{% I18n_Headers %}and it will default to your site.url
With this SEO, each page click for one sites language will count towards the net clicks of all languages on the website.
hello, and welcome to a sample page
please enjoy your stay
This sample text came from a .yml file in the _data directory
html tags are preserved
and links are relativized
If you have installed the jekyll-polyglot gem, these additions to your site header can easily provide your jekyll blog with Google-powered SEO bonuses.
Per W3C Internationalization Best Practices you can set the default language of every page with a meta tag. Just add the following to your header:
<meta http-equiv="Content-Language" content="{{site.active_lang}}">You can easily add hreflang alternate tags to your site, achieving SEO with google multi-language searches. Add the following to your header:
<link rel="alternate"
hreflang="{{site.default_lang}}"
href="http://yoursite.com{{page.permalink}}" />
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
<link rel="alternate"
hreflang="{{lang}}"
href="http://yoursite.com/{{lang}}{{page.permalink}}" />
{% endfor %}You can get all of the above with a single tag added to your header.html:
{% I18n_Headers https://untra.github.com/polyglot %}Just add the permanent url for your website and all of the above SEO will be added to each page in your website. In version >= 1.2.4, you can leave it empty, just calling
{% I18n_Headers %}and it will default to your site.url
With this SEO, each page click for one sites language will count towards the net clicks of all languages on the website.
`,
* or to a parent if there are multiple elements to show.
*/
.message {
margin-bottom: 1rem;
padding: 1rem;
color: #717171;
background-color: #f9f9f9;
}
/*
* Container
*
* Center the page content.
*/
.container {
max-width: 42rem;
padding-left: 1rem;
padding-right: 1rem;
margin-left: auto;
margin-right: auto;
}
/*
* Masthead
*
* Super small header above the content for site name and short description.
*/
.masthead {
padding-top: 1rem;
padding-bottom: 1rem;
margin-bottom: 3rem;
}
.masthead-title {
margin-top: 0;
margin-bottom: 0;
color: #505050;
}
.masthead-title a {
color: #505050;
}
.masthead-title small {
font-size: 75%;
font-weight: 400;
color: #c0c0c0;
letter-spacing: 0;
}
/*
* Posts and pages
*
* Each post is wrapped in `.post` and is used on default and post layouts. Each
* page is wrapped in `.page` and is only used on the page layout.
*/
.page,
.post {
margin-bottom: 4em;
}
/* Blog post or page title */
.page-title,
.post-title,
.post-title a {
color: #303030;
}
.page-title,
.post-title {
margin-top: 0;
}
/* Meta data line below post title */
.post-date {
display: block;
margin-top: -.5rem;
margin-bottom: 1rem;
color: #9a9a9a;
}
/* Related posts */
.related {
padding-top: 2rem;
padding-bottom: 2rem;
border-top: 1px solid #eee;
}
.related-posts {
padding-left: 0;
list-style: none;
}
.related-posts h3 {
margin-top: 0;
}
.related-posts li small {
font-size: 75%;
color: #999;
}
.related-posts li a:hover {
color: #268bd2;
text-decoration: none;
}
.related-posts li a:hover small {
color: inherit;
}
/*
* Pagination
*
* Super lightweight (HTML-wise) blog pagination. `span`s are provide for when
* there are no more previous or next posts to show.
*/
.pagination {
overflow: hidden; /* clearfix */
margin-left: -1rem;
margin-right: -1rem;
font-family: "PT Sans", Helvetica, Arial, sans-serif;
color: #ccc;
text-align: center;
}
/* Pagination items can be `span`s or `a`s */
.pagination-item {
display: block;
padding: 1rem;
border: 1px solid #eee;
}
.pagination-item:first-child {
margin-bottom: -1px;
}
/* Only provide a hover state for linked pagination items */
a.pagination-item:hover {
background-color: #f5f5f5;
}
@media (min-width: 30em) {
.pagination {
margin: 3rem 0;
}
.pagination-item {
float: left;
width: 50%;
}
.pagination-item:first-child {
margin-bottom: 0;
border-top-left-radius: 4px;
border-bottom-left-radius: 4px;
}
.pagination-item:last-child {
margin-left: -1px;
border-top-right-radius: 4px;
border-bottom-right-radius: 4px;
}
}
polyglot-1.5.0/site/public/css/syntax.css 0000664 0000000 0000000 00000006627 14074562261 0020462 0 ustar 00root root 0000000 0000000 .highlight .hll { background-color: #ffc; }
.highlight .c { color: #999; } /* Comment */
.highlight .err { color: #a00; background-color: #faa } /* Error */
.highlight .k { color: #069; } /* Keyword */
.highlight .o { color: #555 } /* Operator */
.highlight .cm { color: #09f; font-style: italic } /* Comment.Multiline */
.highlight .cp { color: #099 } /* Comment.Preproc */
.highlight .c1 { color: #999; } /* Comment.Single */
.highlight .cs { color: #999; } /* Comment.Special */
.highlight .gd { background-color: #fcc; border: 1px solid #c00 } /* Generic.Deleted */
.highlight .ge { font-style: italic } /* Generic.Emph */
.highlight .gr { color: #f00 } /* Generic.Error */
.highlight .gh { color: #030; } /* Generic.Heading */
.highlight .gi { background-color: #cfc; border: 1px solid #0c0 } /* Generic.Inserted */
.highlight .go { color: #aaa } /* Generic.Output */
.highlight .gp { color: #009; } /* Generic.Prompt */
.highlight .gs { } /* Generic.Strong */
.highlight .gu { color: #030; } /* Generic.Subheading */
.highlight .gt { color: #9c6 } /* Generic.Traceback */
.highlight .kc { color: #069; } /* Keyword.Constant */
.highlight .kd { color: #069; } /* Keyword.Declaration */
.highlight .kn { color: #069; } /* Keyword.Namespace */
.highlight .kp { color: #069 } /* Keyword.Pseudo */
.highlight .kr { color: #069; } /* Keyword.Reserved */
.highlight .kt { color: #078; } /* Keyword.Type */
.highlight .m { color: #f60 } /* Literal.Number */
.highlight .s { color: #d44950 } /* Literal.String */
.highlight .na { color: #4f9fcf } /* Name.Attribute */
.highlight .nb { color: #366 } /* Name.Builtin */
.highlight .nc { color: #0a8; } /* Name.Class */
.highlight .no { color: #360 } /* Name.Constant */
.highlight .nd { color: #99f } /* Name.Decorator */
.highlight .ni { color: #999; } /* Name.Entity */
.highlight .ne { color: #c00; } /* Name.Exception */
.highlight .nf { color: #c0f } /* Name.Function */
.highlight .nl { color: #99f } /* Name.Label */
.highlight .nn { color: #0cf; } /* Name.Namespace */
.highlight .nt { color: #2f6f9f; } /* Name.Tag */
.highlight .nv { color: #033 } /* Name.Variable */
.highlight .ow { color: #000; } /* Operator.Word */
.highlight .w { color: #bbb } /* Text.Whitespace */
.highlight .mf { color: #f60 } /* Literal.Number.Float */
.highlight .mh { color: #f60 } /* Literal.Number.Hex */
.highlight .mi { color: #f60 } /* Literal.Number.Integer */
.highlight .mo { color: #f60 } /* Literal.Number.Oct */
.highlight .sb { color: #c30 } /* Literal.String.Backtick */
.highlight .sc { color: #c30 } /* Literal.String.Char */
.highlight .sd { color: #c30; font-style: italic } /* Literal.String.Doc */
.highlight .s2 { color: #c30 } /* Literal.String.Double */
.highlight .se { color: #c30; } /* Literal.String.Escape */
.highlight .sh { color: #c30 } /* Literal.String.Heredoc */
.highlight .si { color: #a00 } /* Literal.String.Interpol */
.highlight .sx { color: #c30 } /* Literal.String.Other */
.highlight .sr { color: #3aa } /* Literal.String.Regex */
.highlight .s1 { color: #c30 } /* Literal.String.Single */
.highlight .ss { color: #fc3 } /* Literal.String.Symbol */
.highlight .bp { color: #366 } /* Name.Builtin.Pseudo */
.highlight .vc { color: #033 } /* Name.Variable.Class */
.highlight .vg { color: #033 } /* Name.Variable.Global */
.highlight .vi { color: #033 } /* Name.Variable.Instance */
.highlight .il { color: #f60 } /* Literal.Number.Integer.Long */
.css .o,
.css .o + .nt,
.css .nt + .nt { color: #999; }
polyglot-1.5.0/site/public/favicon.ico 0000664 0000000 0000000 00000000473 14074562261 0017744 0 ustar 00root root 0000000 0000000 PNG
IHDR pHYs H H Fk> vpAg IDATHcTRTd%`
X0f͘)~pޤT'{x{c*8zP\B>`d$ |p=d
Hy`Ԃ` 6`>`dZh$x+WBسf`úuDY{ny9w
?z)8ڲb 69 "zTXtSoftware xsLOJUMLO
JML /Ԯ M IENDB` polyglot-1.5.0/site/sample.md 0000664 0000000 0000000 00000000416 14074562261 0016145 0 ustar 00root root 0000000 0000000 ---
layout: page
title: Sample rich text data
permalink: sample/
lang: site.data["active_lang"]
---
{{ site.data["sample"][1] }}
{{ site.data["sample"][2] }}
{{ site.data["sample"][3] }}
{{ site.data["sample"][4] }}
{{ site.data["sample"][5] }}
polyglot-1.5.0/site/seo.md 0000664 0000000 0000000 00000003641 14074562261 0015455 0 ustar 00root root 0000000 0000000 ---
layout: page
title: SEO Recipes
permalink: seo/
lang: en
---
# Recipes for Search Engine Optimization using Polyglot
If you have installed the `jekyll-polyglot` gem, these additions to your site header can easily provide your jekyll blog with Google-powered SEO bonuses.
## HTML Language Declaration
Per [W3C Internationalization Best Practices](http://www.w3.org/International/geo/html-tech/tech-lang.html#ri20060630.133615821)
you can set the default language of every page with a meta tag. Just add the following to your header:
{% highlight html %}{% raw %}
{% endraw %}
{% endhighlight %}
## Multi-language SEO using hreflang alternate tags
You can easily add [hreflang alternate tags](https://support.google.com/webmasters/answer/189077?hl=en)
to your site, achieving SEO with google multi-language searches. Add the following to your header:
{% highlight html %}
{% raw %}
{% for lang in site.languages %}
{% if lang == site.default_lang %}
{% continue %}
{% endif %}
{% endfor %}
{% endraw %}
{% endhighlight %}
## All of the above
You can get all of the above with a single tag added to your `header.html`:
{% highlight html %}
{% raw %}
{% I18n_Headers https://untra.github.com/polyglot %}
{% endraw %}
{% endhighlight %}
Just add the permanent url for your website and all of the above SEO will be added to each page in your website.
In version >= 1.2.4, you can leave it empty, just calling
{% highlight html %}
{% raw %}
{% I18n_Headers %}
{% endraw %}
{% endhighlight %}
and it will default to your `site.url`
With this SEO, each page click for one sites language will count towards the net clicks of all languages on the website.
polyglot-1.5.0/spec/ 0000775 0000000 0000000 00000000000 14074562261 0014327 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/fixture/ 0000775 0000000 0000000 00000000000 14074562261 0016015 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/fixture/_.config.yml 0000664 0000000 0000000 00000000422 14074562261 0020220 0 ustar 00root root 0000000 0000000 # Where things are
source: .
destination: ./_site
include: ['pages']
collections:
pages:
output: true
posts:
output: true
#Polyglot
languages: ["en", "es", "fr"]
default_lang: "en"
exclude_from_localization: ["javascript", "images", "css", "public"]
polyglot-1.5.0/spec/fixture/pages/ 0000775 0000000 0000000 00000000000 14074562261 0017114 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/fixture/pages/en.about.md 0000664 0000000 0000000 00000000073 14074562261 0021151 0 ustar 00root root 0000000 0000000 ---
title: About
permalink: about
lang: en
---
# about us
polyglot-1.5.0/spec/fixture/pages/en.menu.md 0000664 0000000 0000000 00000000065 14074562261 0021004 0 ustar 00root root 0000000 0000000 ---
title: Menu
permalink: menu
lang: en
---
# menu
polyglot-1.5.0/spec/fixture/pages/es.menu.md 0000664 0000000 0000000 00000000066 14074562261 0021012 0 ustar 00root root 0000000 0000000 ---
title: Menu
permalink: menu
lang: es
---
# menú
polyglot-1.5.0/spec/fixture/pages/es.samba.md 0000664 0000000 0000000 00000000115 14074562261 0021124 0 ustar 00root root 0000000 0000000 ---
title: samba
permalink: samba
lang: es
lang-exclusive: [es]
---
# samba
polyglot-1.5.0/spec/fixture/pages/fr.members.md 0000664 0000000 0000000 00000000123 14074562261 0021472 0 ustar 00root root 0000000 0000000 ---
title: membres
permalink: members
lang: fr
lang-exclusive: [fr]
---
# membres
polyglot-1.5.0/spec/fixture/pages/fr.menu.md 0000664 0000000 0000000 00000000077 14074562261 0021014 0 ustar 00root root 0000000 0000000 ---
title: Menu
permalink: menu
lang: fr
---
# français menu
polyglot-1.5.0/spec/jekyll/ 0000775 0000000 0000000 00000000000 14074562261 0015621 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/jekyll/polyglot/ 0000775 0000000 0000000 00000000000 14074562261 0017472 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/jekyll/polyglot/hooks/ 0000775 0000000 0000000 00000000000 14074562261 0020615 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/jekyll/polyglot/hooks/coordinate_spec.rb 0000664 0000000 0000000 00000010211 14074562261 0024276 0 ustar 00root root 0000000 0000000 require 'rspec/helper'
require 'ostruct'
require 'fileutils'
require 'tmpdir'
require_relative '../../../../lib/jekyll/polyglot/hooks/coordinate'
Dir.mktmpdir do |_|
FileUtils.mkdir_p 'css'
FileUtils.mkdir_p 'images'
FileUtils.mkdir_p 'javascript'
describe 'hook_coordinate' do
before do
@config = Jekyll::Configuration::DEFAULTS.dup
@langs = ['en', 'fr', 'es']
@default_lang = 'en'
@exclude_from_localization = ['javascript', 'images', 'css/', 'README.md']
@config['langs'] = @langs
@config['default_lang'] = @default_lang
@config['exclude_from_localization'] = @exclude_from_localization
@parallel_localization = @config['parallel_localization'] || true
@site = Site.new(
Jekyll.configuration(
'languages' => @langs,
'default_lang' => @default_lang,
'exclude_from_localization' => @exclude_from_localization,
'source' => File.expand_path('../../../../fixture', __FILE__)
)
)
@site.prepare
@collection = Jekyll::Collection.new(@site, "fixture")
@site.data = { 'foo' => 'databar', 'baz' => 'databaz', 'strings' => {
'banana' => 'banana',
}, }
@site.data['en'] = { 'foo' => 'enbar', 'strings' => {
'apple' => 'apple', 'ice cream' => 'ice cream',
}, }
@site.data['fr'] = { 'foo' => 'frbar', 'strings' => {
'ice cream' => 'crème glacée',
}, }
end
it 'should have trailing / on all dir entries in exclude_from_localization' do
expect(@site.exclude_from_localization).to eq(["javascript/", "images/", "css/", "README.md"])
end
it 'should merge the site.data.active_lang to the site.data' do
hook_coordinate(@site)
expect(@site.data['foo']).to eq('enbar')
expect(@site.data['baz']).to eq('databaz')
expect(@site.data['strings']['ice cream']).to eq('ice cream')
expect(@site.data['strings']['apple']).to eq('apple')
expect(@site.data['strings']['banana']).to eq('banana')
end
it 'should fall back to the default_lang when using translated site data' do
@site.active_lang = 'fr'
hook_coordinate(@site)
expect(@site.data['foo']).to eq('frbar')
expect(@site.data['baz']).to eq('databaz')
expect(@site.data['strings']['ice cream']).to eq('crème glacée') # Populated from @site.data['strings'][@site.active_lang]['ice cream']
expect(@site.data['strings']['apple']).to eq('apple') # Populated from @site.data['strings'][@site.default_lang]['apple']
expect(@site.data['strings']['banana']).to eq('banana') # Populated from @site.data['strings']['apple']
end
describe @coordinate_documents do
it 'test fixtures in the default lang' do
expect(@site.source).to end_with('spec/fixture')
@site.process_language 'en'
expect(@site.pages).to have_attributes(size: 2)
end
it 'should include files in the default_lang without active_lang' do
@site.process_language 'fr'
expect(@site.pages).to have_attributes(size: 3)
expect(@site.pages.map { |doc| doc.name }).to include('en.about.md')
end
it 'should include files in the active_lang' do
@site.process_language 'fr'
expect(@site.pages).to have_attributes(size: 3)
expect(@site.pages.map { |doc| doc.name }).to include('fr.menu.md', 'fr.members.md')
end
it 'should not include files in the default_lang with the active_lang' do
@site.process_language 'fr'
expect(@site.pages.map { |doc| doc.name }).not_to include('en.menu.md')
end
it 'should not include files in a different lang from the active_lang' do
@site.process_language 'fr'
expect(@site.pages.map { |doc| doc.name }).not_to include('es.menu.md')
end
it 'should not be included if the active_lang is not part of the lang-exclusive' do
@site.process_language 'fr'
expect(@site.pages.map { |doc| doc.name }).not_to include('es.samba.md')
end
end
end
end
polyglot-1.5.0/spec/jekyll/polyglot/patches/ 0000775 0000000 0000000 00000000000 14074562261 0021121 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/jekyll/polyglot/patches/jekyll/ 0000775 0000000 0000000 00000000000 14074562261 0022413 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/jekyll/polyglot/patches/jekyll/site_spec.rb 0000664 0000000 0000000 00000026334 14074562261 0024726 0 ustar 00root root 0000000 0000000 require 'jekyll'
require 'rspec/helper'
require 'ostruct'
describe Site do
before do
@config = Jekyll::Configuration::DEFAULTS.dup
@langs = ['en', 'sp', 'fr', 'de']
@default_lang = 'en'
@exclude_from_localization = ['javascript/', 'images/', 'css/', 'readme']
@config['langs'] = @langs
@config['default_lang'] = @default_lang
@config['exclude_from_localization'] = @exclude_from_localization
@parallel_localization = @config['parallel_localization'] || true
@site = Site.new(
Jekyll.configuration(
'languages' => @langs,
'default_lang' => @default_lang,
'exclude_from_localization' => @exclude_from_localization,
'source' => File.expand_path('fixtures', __dir__)
)
)
@site.prepare
@baseurls = ['/polyglot', '/big-brother', '/bas3url2']
@urls = ['http://localhost:4000', 'https://test.github.io']
@document_url_regex = @site.document_url_regex
@relative_url_regex = @site.relative_url_regex
# @relativize_absolute_urls = @site.relativize_absolute_urls
# @relativize_urls = @site.relativize_urls
end
describe @document_url_regex do
it 'must match common default urls made by jekyll' do
@langs.each do |lang|
expect match "/#{lang}/foobar"
expect match ".#{lang}/foobar"
expect match "foobar.#{lang}/"
end
end
it 'expect not match natural unfortunate urls' do
expect(@document_url_regex).to_not match 'people/karen/foobar/'
expect(@document_url_regex).to_not match 'verbs/gasp/foobar'
expect(@document_url_regex).to_not match 'products/kefr/foobar.html'
expect(@document_url_regex).to_not match 'properties/beachside/foo'
end
end
describe @parallel_localization do
it 'should default to true if parallel_localization if not set' do
expect(@parallel_localization).to eq(true)
end
it 'should be false if explicitly set' do
@config['parallel_localization'] = false
@parallel_localization = @config['parallel_localization']
expect(@parallel_localization).to eq(false)
end
end
describe @relative_url_regex do
it 'must match certain strings with any simple baseurl' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@relative_url_regex = @site.relative_url_regex
expect(@relative_url_regex).to match "href=\"#{baseurl}/about/\""
expect(@relative_url_regex).to match "href=\"#{baseurl}/about-the-product/\""
expect(@relative_url_regex).to match "href=\"#{baseurl}/2016/all-new-flavors/\""
expect(@relative_url_regex).to match "href=\"#{baseurl}/words-1-with-2-numbers-34/\""
expect(@relative_url_regex).to match "href=\"#{baseurl}/\""
expect(@relative_url_regex).to match "href=\"#{baseurl}/purchase/product/1234-business\""
end
end
it 'must match with an empty baseurl' do
@relative_url_regex = @site.relative_url_regex
expect(@relative_url_regex).to match 'href="/about/"'
expect(@relative_url_regex).to match 'href="/about-the-product/"'
expect(@relative_url_regex).to match 'href="/2016/all-new-flavors/"'
expect(@relative_url_regex).to match 'href="/2016/words-1-with-2-numbers-34/"'
expect(@relative_url_regex).to match 'href="/"'
expect(@relative_url_regex).to match 'href="/purchase/product/1234-business"'
end
it 'must not match external urls' do
@relative_url_regex = @site.relative_url_regex
expect(@relative_url_regex).to_not match 'href="http://github.com"'
expect(@relative_url_regex).to_not match 'href="https://talk.jekyllrb.com'
expect(@relative_url_regex).to_not match 'href="http://google.com"'
expect(@relative_url_regex).to_not match 'href="https://untra.github.io/polyglot"'
end
it 'must not match excluded urls' do
@site.exclude += @exclude_from_localization
@relative_url_regex = @site.relative_url_regex
expect(@relative_url_regex).to_not match 'href="/images/my-vacation-photo.jpg"'
expect(@relative_url_regex).to_not match 'href="/css/stylesheet.css"'
expect(@relative_url_regex).to_not match 'href="/readme"'
expect(@relative_url_regex).to_not match 'href="/javascript/65487-app.js"'
end
it 'must not match excluded urls with a set baseurl' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@site.exclude += @exclude_from_localization
@relative_url_regex = @site.relative_url_regex
expect(@relative_url_regex).to_not match "href=\"#{baseurl}/javascript/65487-app.js\""
expect(@relative_url_regex).to_not match "href=\"#{baseurl}/images/my-vacation-photo.jpg\""
expect(@relative_url_regex).to_not match "href=\"#{baseurl}/css/stylesheet.css\""
end
end
it 'must not match localized urls' do
@relative_url_regex = @site.relative_url_regex
@langs.each do |lang|
expect(@relative_url_regex).to_not match "href=\"#{lang}/about/\""
expect(@relative_url_regex).to_not match "href=\"#{lang}/\""
expect(@relative_url_regex).to_not match "href=\"#{lang}/purchase/product/1234-business\""
end
end
it 'must not match localized urls with a set baseurl' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@site.exclude += @exclude_from_localization
@relative_url_regex = @site.relative_url_regex
expect(@relative_url_regex).to_not match "href=\"#{baseurl}/javascript/65487-app.js\""
expect(@relative_url_regex).to_not match "href=\"#{baseurl}/images/my-vacation-photo.jpg\""
expect(@relative_url_regex).to_not match "href=\"#{baseurl}/css/stylesheet.css\""
end
end
it 'disabled relativization must match ferh relative url with baseurl' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@urls.each do |url|
@site.config['url'] = url
@relative_url_regex = @site.relative_url_regex(true)
expect(@relative_url_regex).to match "ferh=\"#{baseurl}/about/\""
expect(@relative_url_regex).to match "ferh=\"#{baseurl}/about-the-product/\""
expect(@relative_url_regex).to match "ferh=\"#{baseurl}/2016/all-new-flavors/\""
expect(@relative_url_regex).to match "ferh=\"#{baseurl}/words-1-with-2-numbers-34/\""
expect(@relative_url_regex).to match "ferh=\"#{baseurl}/\""
expect(@relative_url_regex).to match "ferh=\"#{baseurl}/purchase/product/1234-business\""
end
end
end
end
describe @absolute_url_regex do
it 'must match absolute url' do
@urls.each do |url|
@site.config['url'] = url
@site.prepare
@absolute_url_regex = @site.absolute_url_regex(url)
expect(@absolute_url_regex).to match "href=\"#{url}/javascript/65487-app.js\""
expect(@absolute_url_regex).to match "href=\"#{url}/images/my-vacation-photo.jpg\""
expect(@absolute_url_regex).to match "href=\"#{url}/css/stylesheet.css\""
end
end
it 'must match absolute url' do
@urls.each do |url|
@site.config['url'] = url
@absolute_url_regex = @site.absolute_url_regex(url)
expect(@absolute_url_regex).to match "href=\"#{url}/javascript/65487-app.js\""
expect(@absolute_url_regex).to match "href=\"#{url}/images/my-vacation-photo.jpg\""
expect(@absolute_url_regex).to match "href=\"#{url}/css/stylesheet.css\""
end
end
it 'must not match absolute url for another project' do
@urls.each do |url|
@site.config['url'] = url
@absolute_url_regex = @site.absolute_url_regex(url)
expect(@absolute_url_regex).to_not match 'href="http://test_github.io/javascript/65487-app.js'
expect(@absolute_url_regex).to_not match 'href="http://test_github.io/images/my-vacation-photo.jpg'
expect(@absolute_url_regex).to_not match 'href="http://github.io/css/stylesheet.css'
end
end
it 'must not match whitespaced urls' do
@urls.each do |url|
@site.config['url'] = url
@absolute_url_regex = @site.absolute_url_regex(url)
expect(@absolute_url_regex).to_not match "href=\" #{url}/javascript/65487-app.js\""
expect(@absolute_url_regex).to_not match "href=\" #{url}/images/my-vacation-photo.jpg\""
expect(@absolute_url_regex).to_not match "href=\" #{url}/css/stylesheet.css\" "
end
end
it 'must match absolute url with baseurl' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@urls.each do |url|
@site.config['url'] = url
@absolute_url_regex = @site.absolute_url_regex(url)
expect(@absolute_url_regex).to match " href=\"#{url}#{baseurl}/javascript/65487-app.js\""
expect(@absolute_url_regex).to match " href=\"#{url}#{baseurl}/images/my-vacation-photo.jpg\""
expect(@absolute_url_regex).to match " href=\"#{url}#{baseurl}/css/stylesheet.css\""
end
end
end
it 'disabled relativization must match ferh absolute url with baseurl' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@urls.each do |url|
@site.config['url'] = url
@absolute_url_regex = @site.absolute_url_regex(url, true)
expect(@absolute_url_regex).to match "ferh=\"#{url}#{baseurl}/javascript/65487-app.js\""
expect(@absolute_url_regex).to match "ferh=\"#{url}#{baseurl}/images/my-vacation-photo.jpg\""
expect(@absolute_url_regex).to match "ferh=\"#{url}#{baseurl}/css/stylesheet.css\""
end
end
end
it 'negative lookbehind for hreflang, which god help me if this severely hampers performance' do
@baseurls.each do |baseurl|
@site.baseurl = baseurl
@urls.each do |url|
@site.config['url'] = url
@absolute_url_regex = @site.absolute_url_regex(url)
expect(@absolute_url_regex).to_not match ""
expect(@absolute_url_regex).to match ""
end
end
end
end
describe @site do
it 'should copy active_lang to additional variables' do
@site.config['lang_vars'] = [ 'locale', 'язык' ]
@site.prepare
@langs.each do |lang|
@site.active_lang = lang
expect(@site.site_payload['site']['locale']).to match lang
expect(@site.site_payload['site']['язык']).to match lang
end
end
end
describe @site do
it 'should spawn no more than Etc.nprocessors processes' do
forks = 0
allow(Etc).to receive(:nprocessors).and_return(2)
allow(@site).to receive(:fork) { forks += 1; fork { sleep 2 } }
thr = Thread.new { sleep 1; forks }
@site.process
expect(thr.value).to eq(Etc.nprocessors)
expect(forks).to eq((@langs + [@default_lang]).uniq.length)
end
end
# describe @relativize_urls do
# it 'does not raise' do
# expect(@relativize_urls(@site.Document.new(), @relative_url_regex)).not_to raise_error
# end
# end
# describe @relativize_absolute_urls do
# it 'does not raise' do
# expect( @relativize_absolute_urls(@site.Document.new(), @absolute_url_regex)).not_to raise_error
# end
# end
end
polyglot-1.5.0/spec/jekyll/polyglot/patches/jekyll/static_file_spec.rb 0000664 0000000 0000000 00000000000 14074562261 0026226 0 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/rspec/ 0000775 0000000 0000000 00000000000 14074562261 0015443 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/rspec/helper.rb 0000664 0000000 0000000 00000000321 14074562261 0017243 0 ustar 00root root 0000000 0000000 require "rspec"
require 'rspec/mocks'
# require 'minitest/autorun'
require "jekyll/polyglot"
require "jekyll"
Dir[File.expand_path("../../support/*.rb", __FILE__)].each do |v|
require v
end
include Jekyll
polyglot-1.5.0/spec/spec_helper.rb 0000664 0000000 0000000 00000011436 14074562261 0017152 0 ustar 00root root 0000000 0000000 # This file was generated by the `rspec --init` command. Conventionally, all
# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
# The generated `.rspec` file contains `--require spec_helper` which will cause
# this file to always be loaded, without a need to explicitly require it in any
# files.
#
# Given that it is always loaded, you are encouraged to keep this file as
# light-weight as possible. Requiring heavyweight dependencies from this file
# will add to the boot time of your test suite on EVERY test run, even for an
# individual file that may not need all of that loaded. Instead, consider making
# a separate helper file that requires the additional dependencies and performs
# the additional setup, and require it from the spec files that actually need
# it.
#
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
RSpec.configure do |config|
# rspec-expectations config goes here. You can use an alternate
# assertion/expectation library such as wrong or the stdlib/minitest
# assertions if you prefer.
config.expect_with :rspec do |expectations|
# This option will default to `true` in RSpec 4. It makes the `description`
# and `failure_message` of custom matchers include text for helper methods
# defined using `chain`, e.g.:
# be_bigger_than(2).and_smaller_than(4).description
# # => "be bigger than 2 and smaller than 4"
# ...rather than:
# # => "be bigger than 2"
expectations.include_chain_clauses_in_custom_matcher_descriptions = true
end
# rspec-mocks config goes here. You can use an alternate test double
# library (such as bogus or mocha) by changing the `mock_with` option here.
config.mock_with :rspec do |mocks|
# Prevents you from mocking or stubbing a method that does not exist on
# a real object. This is generally recommended, and will default to
# `true` in RSpec 4.
mocks.verify_partial_doubles = true
end
# This option will default to `:apply_to_host_groups` in RSpec 4 (and will
# have no way to turn it off -- the option exists only for backwards
# compatibility in RSpec 3). It causes shared context metadata to be
# inherited by the metadata hash of host groups and examples, rather than
# triggering implicit auto-inclusion in groups with matching metadata.
config.shared_context_metadata_behavior = :apply_to_host_groups
# The settings below are suggested to provide a good initial experience
# with RSpec, but feel free to customize to your heart's content.
=begin
# This allows you to limit a spec run to individual examples or groups
# you care about by tagging them with `:focus` metadata. When nothing
# is tagged with `:focus`, all examples get run. RSpec also provides
# aliases for `it`, `describe`, and `context` that include `:focus`
# metadata: `fit`, `fdescribe` and `fcontext`, respectively.
config.filter_run_when_matching :focus
# Allows RSpec to persist some state between runs in order to support
# the `--only-failures` and `--next-failure` CLI options. We recommend
# you configure your source control system to ignore this file.
config.example_status_persistence_file_path = "spec/examples.txt"
# Limits the available syntax to the non-monkey patched syntax that is
# recommended. For more details, see:
# - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
# - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
# - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
config.disable_monkey_patching!
# This setting enables warnings. It's recommended, but in some cases may
# be too noisy due to issues in dependencies.
config.warnings = true
# Many RSpec users commonly either run the entire suite or an individual
# file, and it's useful to allow more verbose output when running an
# individual spec file.
if config.files_to_run.one?
# Use the documentation formatter for detailed output,
# unless a formatter has already been configured
# (e.g. via a command-line flag).
config.default_formatter = "doc"
end
# Print the 10 slowest examples and example groups at the
# end of the spec run, to help surface which specs are running
# particularly slow.
config.profile_examples = 10
# Run specs in random order to surface order dependencies. If you find an
# order dependency and want to debug it, you can fix the order by providing
# the seed, which is printed after each run.
# --seed 1234
config.order = :random
# Seed global randomization in this process using the `--seed` CLI option.
# Setting this allows you to use `--seed` to deterministically reproduce
# test failures related to randomization by passing the same `--seed` value
# as the one that triggered the failure.
Kernel.srand config.seed
=end
end
polyglot-1.5.0/spec/support/ 0000775 0000000 0000000 00000000000 14074562261 0016043 5 ustar 00root root 0000000 0000000 polyglot-1.5.0/spec/support/jekyll.rb 0000664 0000000 0000000 00000014520 14074562261 0017664 0 ustar 00root root 0000000 0000000 # ----------------------------------------------------------------------------
# Frozen-string-literal: true
# Copyright: 2012 - 2016 - MIT License
# Encoding: utf-8
# ----------------------------------------------------------------------------
require "nokogiri"
module Jekyll
module RSpecHelpers
class ContextThief < Liquid::Tag
class << self
attr_accessor :context
end
# ----------------------------------------------------------------------
def render(context)
self.class.context = context
end
end
# ------------------------------------------------------------------------
# Allows you to get a real context context, to test methods directly
# if you need to, most can be tested indirectly.
# ------------------------------------------------------------------------
def build_context
site = stub_jekyll_site
site.liquid_renderer.file("").parse("{% context_thief %}") \
.render!(site.site_payload, :registers => { :site => site })
ContextThief.context
end
# ------------------------------------------------------------------------
def fragment(html)
Nokogiri::HTML.fragment(html)
end
# ------------------------------------------------------------------------
# Allows you to run something capturing all errors and output so you can
# run a test cleanly without a bunch of noise, nobody likes noise when they
# are just trying to see the result of a failed test.
# ------------------------------------------------------------------------
def silence_stdout(return_stringio = false)
old_stdout = $stdout; old_stderr = $stderr
$stdout = stdout = StringIO.new
$stderr = stderr = StringIO.new
output = yield
if return_stringio
return [
stdout.string,
stderr.string
]
else
return output
end
ensure
$stdout = old_stdout
$stderr = old_stderr
end
# ------------------------------------------------------------------------
# Uses `#silence_stdout` to return output to you without you having
# to use true or false on `#silence_stoudt`.
# ------------------------------------------------------------------------
def capture_stdout(&block)
silence_stdout true, &block
end
# ------------------------------------------------------------------------
# Stubs the asset config on Jekyll for you, this is meant to be used
# in a new context or at the top of a context so that you can stub the
# configuration and have it reset afterwards.
# ------------------------------------------------------------------------
def stub_asset_config(inst, hash = nil)
(hash = inst; inst = nil) if inst.is_a?(Hash)
inst = @site || site unless inst
hash = Jekyll::Assets::Config.merge(hash)
allow(inst).to receive(:config).and_return(inst.config.merge({
"assets" => hash
}))
end
# ------------------------------------------------------------------------
def stub_env_config(inst, hash = nil)
(hash = inst; inst = nil) if inst.is_a?(Hash)
inst = @env || env unless inst
hash = Jekyll::Utils.deep_merge_hashes(inst.asset_config, hash)
allow(inst).to receive(:asset_config).and_return(hash)
end
# ------------------------------------------------------------------------
# Strips ANSI from the output so that you can test just a plain text
# string without worrying about whether colors are there or not, this is
# mostly useful for testing log output or other helpers.
# ------------------------------------------------------------------------
def strip_ansi(str)
str.gsub(/\e\[(?:\d+)(?:;\d+)?m/, "")
end
# ------------------------------------------------------------------------
# Stubs the Jekyll site with your configuration, most of the time you
# won't do it this way though, because you can just initialize the default
# configuration with our merges and stub the configuration pieces.
# ------------------------------------------------------------------------
def stub_jekyll_site(opts = {})
path = File.expand_path("../../fixture", __FILE__)
Jekyll::RSpecHelpers.cleanup_trash
silence_stdout do
Jekyll::Site.new(Jekyll.configuration(opts.merge({
"source" => path, "destination" => File.join(path, "_site")
}))).tap(&:read)
end
end
# ------------------------------------------------------------------------
# See: `#stub_jekyll_site` except this also kicks a process so that
# do both the building and the processing all in one shot.
# ------------------------------------------------------------------------
def stub_jekyll_site_with_processing(oth_opts = {})
site = stub_jekyll_site(oth_opts)
silence_stdout { site.process }
site
end
# ------------------------------------------------------------------------
# Pulls a file and passes the data to you (from _site), this does
# no checking so it will raise an error if there is no file that you wish
# to pull, so beware of that when testing.
# ------------------------------------------------------------------------
def get_stubbed_file(file)
path = File.expand_path("../../fixture/_site", __FILE__)
File.read(File.join(path, file))
end
# ------------------------------------------------------------------------
# Cleanup after ourselves when testing, removing the data that we and
# through us Jekyll created, so that if we test again there is nothing but
# clean data to test with, and not dirty old data.
# ------------------------------------------------------------------------
def self.cleanup_trash
%W(.asset-cache .jekyll-metadata _site).each do |v|
FileUtils.rm_rf(File.join(File.expand_path("../../fixture", __FILE__), v))
end
end
end
end
# ----------------------------------------------------------------------------
Liquid::Template.register_tag "context_thief", \
Jekyll::RSpecHelpers::ContextThief
# ----------------------------------------------------------------------------
RSpec.configure do |c|
c.include Jekyll::RSpecHelpers
c.before :all do
Jekyll::RSpecHelpers.cleanup_trash
end
#
c.after :all do
Jekyll::RSpecHelpers.cleanup_trash
end
end