makeloc 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +2 -2
- data/VERSION +1 -1
- data/makeloc.gemspec +2 -2
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: bdb1551cf52782393df61fe7a9e3030f1afd3d75
|
4
|
+
data.tar.gz: 6b5faa4fc45c96d471fb20336c625b309221b725
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: aed2bea2495ab47d716bc10c8e6c1c2d5d77406232cd1dd00f02c70eb96a090785e14d705a8220e2a45e4406fa462ec0045827ebbb9bf5b502888511c715ca70
|
7
|
+
data.tar.gz: fedd1115e3ff5076e525963c133bd43ba0b599aaf38c115111b1d3705c21d0dc030ce25e2108438de1a4ebce621a1e127ba0d4c8c00b909ff6320502589c25a4
|
data/README.md
CHANGED
@@ -1,10 +1,10 @@
|
|
1
1
|
# Makeloc
|
2
|
-
A little generator to tidy locale
|
2
|
+
A little generator to tidy locale files along with their contents for Ruby On Rails
|
3
3
|
|
4
4
|
## Idea
|
5
5
|
Makeloc comes from the necessity to update or create locale files while developing Ruby on Rails application. Often there is a reference language which get manually updated whenever necessary and later all the other locales should follow the same update steps. This last part could be very tedious and prone to errors or missings.
|
6
6
|
|
7
|
-
Makeloc, given a reference filepath (formatted as `path/to/file/context.reference_lang.yml`) and a target language, creates, in the same folder, a corresponding locale file `path/to/file/context.target_lang.yml` with same keys. If the target file already exists it gets updated. It actually get recreated with the same structure (same keys set) and then updated with old values. This means that keys in the old
|
7
|
+
Makeloc, given a reference filepath (formatted as `path/to/file/context.reference_lang.yml`) and a target language, creates, in the same folder, a corresponding locale file `path/to/file/context.target_lang.yml` with same keys. If the target file already exists it gets updated. It actually get recreated with the same structure (same keys set) of the reference one and then updated with old values. This means that keys in the old target locale file not present in the reference one will be wiped out after generation.
|
8
8
|
|
9
9
|
## Installation
|
10
10
|
gem install makeloc
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.1.
|
1
|
+
0.1.1
|
data/makeloc.gemspec
CHANGED
@@ -2,11 +2,11 @@
|
|
2
2
|
# DO NOT EDIT THIS FILE DIRECTLY
|
3
3
|
# Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
|
4
4
|
# -*- encoding: utf-8 -*-
|
5
|
-
# stub: makeloc 0.1.
|
5
|
+
# stub: makeloc 0.1.1 ruby lib
|
6
6
|
|
7
7
|
Gem::Specification.new do |s|
|
8
8
|
s.name = "makeloc"
|
9
|
-
s.version = "0.1.
|
9
|
+
s.version = "0.1.1"
|
10
10
|
|
11
11
|
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
|
12
12
|
s.require_paths = ["lib"]
|