jekyll-language-plugin 1.1.1 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b0a05d1d865dc59d54dada24d41de3c9d5d615de
-  data.tar.gz: 002e66f66fa993f0abbe721e71a31357562f5cb7
+  metadata.gz: 2b6c261bef7ca88520afb58ec4a1760617681229
+  data.tar.gz: fd4978a18ea984aacdccafb8b43b6c8b20cb6323
 SHA512:
-  metadata.gz: 6410a6d6c6dce3fa4ec4e60bdf6492b4d8979a30930977144171c88734431da6a2fe1d10b85f6addd8ea3ea0005247fdda51dc0eea6c07886db044cfced54cc4
-  data.tar.gz: ae6919a539b02a056908dbb88bb7c28df9bd3f33457feb1ae4ca8993ffb88ead15b1c8c72adf9613a3ff852fba720638f600b9f44a51e37ef1047d35ea5aa4fb
+  metadata.gz: 1528ab446fa8b5446dfa068aa377f669d8933aa4fae6faab3f021fc9c502d1a9b53134398a6fa15e8490a150a3b8f2f1d101da30ad0c119427d20f4900e75986
+  data.tar.gz: 1782d0f93101c1a2dfceaf5783eaf859138f201153dceb0e8f486c2242e246b66106bc0b5bab28969b1c1bb90c7a2c585ecd6d981a337ab921a0d9b8ecba24ec

data/LICENSE.md

@@ -1,7 +1,5 @@
 The MIT License (MIT)
 
-Copyright (c) 2014 GitHub, inc.
-
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights

data/README.md

@@ -53,7 +53,7 @@ The first key, `language_data`, tells the plugin where it can find the translati
 
 ## Usage
 
-Every page or post, that needs to be translated must either have a `language` key or a `languages` array inside its YAML front-matter. Additionally, it may also have an `alias` key which tells the plugin to traverse one step further into the language data. So for example, if `alias` is `home` and the `language_data` configuration setting is `data.lang.%%` and the language is `en`, the plugin will look into `data.lang.en.home` for the translation keys used by the liquid tag. Of course, only pages and layouts can use the translation liquid tag but layouts used by posts can therefore benefit from an `alias`.
+Every page or post, that needs to be translated must either have a `language` key or a `languages` array inside its YAML front-matter. Additionally, it may also have an `subset` key which tells the plugin to traverse one step further into the language data. So for example, if `subset` is `home` and the `language_data` configuration setting is `data.lang.%%` and the language is `en`, the plugin will look into `data.lang.en.home` for the translation keys used by the liquid tag. Of course, only pages and layouts can use the translation liquid tag but layouts used by posts can therefore benefit from an `subset`.
 
 ### Example
 
@@ -62,7 +62,7 @@ This is a page optimized for the language plugin, `home.html`:
 ```
 ---
 layout: default
-alias: home
+subset: home
 languages:
 - en
 - de
@@ -107,7 +107,7 @@ Create a new file `_layouts/default.html` which will contain the default layout:
 </html>
 ```
 
-As a sidenote, if an `alias` is given and the translation liquid tag can not find a key within the alias of a given language, it will look without the `alias`, basically one level upwards.
+As a side note, if a `subset` is given and the translation liquid tag can not find a key within the given subset of the specified language, it will perform another lookup without the given subset.
 
 So if `footnote` is common to all pages and posts, it can be placed within the root of each language file. For the English language, add the following to `_data/lang/en.yml`:
 
@@ -125,7 +125,7 @@ If you now run `jekyll build`, you will obtain two separate `home.html` files in
 
 ### Posts
 
-Similar to pages, posts can also have the `languages` or `language` keys in its YAML front-matter. The `alias` key is also supported. Unlike pages, posts cannot use the translation liquid tag but the layout used by the post can. The post is rendered for each language specified, just like pages are.
+Similar to pages, posts can also have the `languages` or `language` keys as well as the `subset` key in its YAML front-matter. You can use all supported liquid tags and filters to translate posts but you can also create multiple posts, one for each language.
 
 ## Liquid tags
 
@@ -135,9 +135,9 @@ Currently, there are two liquid tags provided by this plugin.
 
 The `t` liquid tag provides a convenient way of accessing language-specific translations from the language data referred to in the configuration file.
 
-If an alias is given by the page's or post's front-matter, `t` will look into the language-specific alias first. Only if the key cannot be found there, it will perform another lookup without the alias. This can be useful for common translations like a copyright notice. The key can also be a dot-notation of multiple keys which are traversed upon lookup.
+If a `subset` is given by the page's or post's front-matter, `t` will look into the given `subset` of the language specified. Only if the key cannot be found there, it will perform another lookup without traversing into the given subset. This can be useful for common translations like a copyright notice. The key can also be a dot-notation of cascaded keys which are traversed upon lookup.
 
-*Example*: `{% t homepage_welcome %}`
+*Example*: `{% t homepage_welcome %}` or `{% t homepage.welcome %}`
 
 ### Language-Specific Include Tag
 

data/lib/jekyll-language-plugin/liquid_context.rb

@@ -23,9 +23,9 @@ module JekyllLanguagePlugin
       data = self.get_language_data(context)
       return "" if data.nil?
 
-      page_alias = context.registers[:page]['alias']
-      if (!page_alias.to_s.empty? &&
-          !(str = traverse_hash(traverse_hash(data, page_alias), key)).to_s.empty?) ||
+      language_subset = context.registers[:page]['subset']
+      if (!language_subset.to_s.empty? &&
+          !(str = traverse_hash(traverse_hash(data, language_subset), key)).to_s.empty?) ||
          !(str = traverse_hash(data, key)).to_s.empty?
         return str
       end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jekyll-language-plugin
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.1.2
 platform: ruby
 authors:
 - Vincent Wochnik
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-11-14 00:00:00.000000000 Z
+date: 2015-11-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jekyll