yury-twine 0.9.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: b5e4de6204261bceed91cc9d750fd293febe2922
+  data.tar.gz: 64334676ef727599a2e6e4dc49d9b4de10ff5f15
+SHA512:
+  metadata.gz: 13c11084a4c44d8371dceb0667fa627f30f800fce2bfad9a342aa5f098d595a2c61343959c89a5966bbbf2a6a3a5028070baa40a972dd90bc8ef1695bd22636e
+  data.tar.gz: 8b85cfc24587d28cc2986d0e87cb890bb07409db391dc01823c26dccc6e5a6ccc30e5835870b621319c5db65b9b0e670d430bf1a46c90944d8c4ba5531e5845b

data/Gemfile

@@ -0,0 +1,2 @@
+source "https://rubygems.org"
+gemspec

data/LICENSE

@@ -0,0 +1,30 @@
+Software License Agreement (BSD License)
+
+Copyright (c) 2012, Mobiata, LLC
+All rights reserved.
+
+Redistribution and use of this software in source and binary forms, with or
+without modification, are permitted provided that the following conditions are
+met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the organization nor the names of its contributors may be
+  used to endorse or promote products derived from this software without
+  specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.md

@@ -0,0 +1,230 @@
+# Twine
+
+Twine is a command line tool for managing your strings and their translations. These are all stored in a master text file and then Twine uses this file to import and export localization files in a variety of types, including iOS and Mac OS X `.strings` files, Android `.xml` files, gettext `.po` files, and [jquery-localize][jquerylocalize] `.json` files. This allows individuals and companies to easily share translations across multiple projects, as well as export localization files in any format the user wants.
+
+## Install
+
+### As a Gem
+
+Twine is most easily installed as a Gem.
+
+	$ gem install twine
+
+### From Source
+
+You can also run Twine directly from source. However, it requires [rubyzip][rubyzip] in order to create and read standard zip files.
+
+	$ gem install rubyzip
+	$ git clone git://github.com/mobiata/twine.git
+	$ cd twine
+	$ ./twine --help
+
+Make sure you run the `twine` executable at the root of the project as it properly sets up your Ruby library path. The `bin/twine` executable does not.
+
+## Twine File Format
+
+Twine stores everything in a single file, the Twine data file. The format of this file is a slight variant of the [Git][git] config file format, which itself is based on the old [Windows INI file][INI] format. The entire file is broken up into sections, which are created by placing the section name between two pairs of square brackets. Sections are optional, but they are the recommended way of grouping your definitions into smaller, more manageable chunks.
+
+Each grouping section contains N definitions. These definitions start with the key placed within a single pair of square brackets. It then contains a number of key-value pairs, including a comment, a comma-separated list of tags and all of the translations.
+
+### Placeholders
+
+Twine supports [`printf` style placeholders][printf] with one peculiarity: `@` is used for strings instead of `s`. This is because Twine started out as a tool for iOS and OS X projects.
+
+### Tags
+
+Tags are used by Twine as a way to only work with a subset of your definitions at any given point in time. Each definition can be assigned zero or more tags which are separated by commas. Tags are optional, though highly recommended. You can get a list of all definitions currently missing tags by executing the [`validate-twine-file`](#validate-twine-file) command with the `--pedantic` option.
+
+When generating a localization file, you can specify which definitions should be included using the `--tags` option. Provide a comma separated list of tags to match all definitions that contain any of the tags (`--tags tag1,tag2` matches all definitions tagged with `tag1` _or_ `tag2`). Provide multiple `--tags` options to match defintions containing all specified tags (`--tags tag1 --tags tag2` matches all definitions tagged with `tag1` _and_ `tag2`). You can match definitions _not_ containing a tag by prefixing the tag with a tilde (`--tags ~tag1` matches all definitions _not_ tagged with `tag1`.). All three options are combinable.
+
+### Whitespace
+
+Whitepace in this file is mostly ignored. If you absolutely need to put spaces at the beginning or end of your translated string, you can wrap the entire string in a pair of `` ` `` characters. If your actual string needs to start *and* end with a grave accent, you can wrap it in another pair of `` ` `` characters. See the example, below.
+
+### References
+
+If you want a definition to inherit the values of another definition, you can use a reference. Any property not specified for a definition will be taken from the reference.
+
+### Example
+
+```ini
+	[[General]]
+		[yes]
+			en = Yes
+			es = Sí
+			fr = Oui
+			ja = はい
+		[no]
+			en = No
+			fr = Non
+			ja = いいえ
+
+	[[Errors]]
+		[path_not_found_error]
+			en = The file '%@' could not be found.
+			tags = app1,app6
+			comment = An error describing when a path on the filesystem could not be found.
+		[network_unavailable_error]
+			en = The network is currently unavailable.
+			tags = app1
+			comment = An error describing when the device can not connect to the internet.
+		[dismiss_error]
+			ref = yes
+			en = Dismiss
+
+	[[Escaping Example]]
+		[list_item_separator]
+			en = `, `
+			tags = mytag
+			comment = A string that should be placed between multiple items in a list. For example: Red, Green, Blue
+		[grave_accent_quoted_string]
+			en = ``%@``
+			tags = myothertag
+			comment = This string will evaluate to `%@`.
+```
+
+## Supported Output Formats
+
+Twine currently supports the following output formats:
+
+* [iOS and OS X String Resources][applestrings] (format: apple)
+* [Android String Resources][androidstrings] (format: android)
+* [Gettext PO Files][gettextpo] (format: gettext)
+* [jquery-localize Language Files][jquerylocalize] (format: jquery)
+* [Django PO Files][djangopo] (format: django)
+* [Tizen String Resources][tizen] (format: tizen)
+
+If you would like to enable Twine to create localization files in another format, read the wiki page on how to create an appropriate formatter.
+
+## Usage
+
+	Usage: twine COMMAND TWINE_FILE [INPUT_OR_OUTPUT_PATH] [--lang LANG1,LANG2...] [--tags TAG1,TAG2,TAG3...] [--format FORMAT]
+
+### Commands
+
+#### `generate-localization-file`
+
+This command creates a localization file from the Twine data file. If the output file would not contain any translations, Twine will exit with an error.
+
+	$ twine generate-localization-file /path/to/twine.txt values-ja.xml --tags common,app1
+	$ twine generate-localization-file /path/to/twine.txt Localizable.strings --lang ja --tags mytag
+	$ twine generate-localization-file /path/to/twine.txt all-english.strings --lang en
+
+#### `generate-all-localization-files`
+
+This command is a convenient way to call [`generate-localization-file`](#generate-localization-file) multiple times. It uses standard conventions to figure out exactly which files to create given a parent directory. For example, if you point it to a parent directory containing `en.lproj`, `fr.lproj`, and `ja.lproj` subdirectories, Twine will create a `Localizable.strings` file of the appropriate language in each of them. However, files that would not contain any translations will not be created; instead warnings will be logged to `stderr`. This is often the command you will want to execute during the build phase of your project.
+
+	$ twine generate-all-localization-files /path/to/twine.txt /path/to/project/locales/directory --tags common,app1
+
+#### `consume-localization-file`
+
+This command slurps all of the translations from a localization file and incorporates the translated strings into the Twine data file. This is a simple way to incorporate any changes made to a single file by one of your translators. It will only identify definitions that already exist in the data file.
+
+	$ twine consume-localization-file /path/to/twine.txt fr.strings
+	$ twine consume-localization-file /path/to/twine.txt Localizable.strings --lang ja
+	$ twine consume-localization-file /path/to/twine.txt es.xml
+
+#### `consume-all-localization-files`
+
+This command reads in a folder containing many localization files. These files should be in a standard folder hierarchy so that Twine knows the language of each file. When combined with the `--developer-language`, `--consume-comments`, and `--consume-all` flags, this command is a great way to create your initial Twine data file from an existing project. Just make sure that you create a blank Twine data file first!
+
+	$ twine consume-all-localization-files twine.txt Resources/Locales --developer-language en --consume-all --consume-comments
+
+#### `generate-loc-drop`
+
+This command is a convenient way to generate a zip file containing files created by the [`generate-localization-file`](#generate-localization-file) command. If a file would not contain any translated strings, it is skipped and a warning is logged to `stderr`. This command can be used to create a single zip containing a large number of translations in all languages which you can then hand off to your translation team.
+
+	$ twine generate-loc-drop /path/to/twine.txt LocDrop1.zip
+	$ twine generate-loc-drop /path/to/twine.txt LocDrop2.zip --lang en,fr,ja,ko --tags common,app1
+
+#### `consume-loc-drop`
+
+This command is a convenient way of taking a zip file and executing the [`consume-localization-file`](#consume-localization-file) command on each file within the archive. It is most often used to incorporate all of the changes made by the translation team after they have completed work on a localization drop.
+
+	$ twine consume-loc-drop /path/to/twine.txt LocDrop2.zip
+
+#### `validate-twine-file`
+
+This command validates that the Twine data file can be parsed, contains no duplicate keys, and that no key contains invalid characters. It will exit with a non-zero status code if any of those criteria are not met.
+
+	$ twine validate-twine-file /path/to/twine.txt
+
+## Creating Your First Twine Data File
+
+The easiest way to create your first Twine data file is to run the [`consume-all-localization-files`](#consume-all-localization-files) command. The one caveat is to first create a blank file to use as your starting point. Then, just point the `consume-all-localization-files` command at a directory in your project containing all of your localization files.
+
+	$ touch twine.txt
+	$ twine consume-all-localization-files twine.txt Resources/Locales --developer-language en --consume-all --consume-comments
+
+## Twine and Your Build Process
+
+### Xcode
+
+It is easy to incorporate Twine right into your iOS and OS X app build processes.
+
+1. In your project folder, create all of the `.lproj` directories that you need. It does not really matter where they are. We tend to put them in `Resources/Locales/`.
+2. Run the [`generate-all-localization-files`](#generate-all-localization-files) command to create all of the `.strings` files you need in these directories. For example,
+
+		$ twine generate-all-localization-files twine.txt Resources/Locales/ --tags tag1,tag2
+
+	Make sure you point Twine at your data file, the directory that contains all of your `.lproj` directories, and the tags that describe the definitions you want to use for this project.
+3. Drag the `Resources/Locales/` directory to the Xcode project navigator so that Xcode knows to include all of these `.strings` files in your build.
+4. In Xcode, navigate to the "Build Phases" tab of your target.
+5. Click on the "Add Build Phase" button and select "Add Run Script".
+6. Drag the new "Run Script" build phase up so that it runs earlier in the build process. It doesn't really matter where, as long as it happens before the resources are copied to your bundle.
+7. Edit your script to run the exact same command you ran in step (2) above.
+
+Now, whenever you build your application, Xcode will automatically invoke Twine to make sure that your `.strings` files are up-to-date.
+
+### Android Studio/Gradle
+
+Add the following task at the top level in app/build.gradle:
+```
+task generateLocalizations {
+    String script = 'if hash twine 2>/dev/null; then twine generate-localization-file twine.txt ./src/main/res/values/generated_strings.xml; fi'
+    exec {
+        executable "sh"
+        args '-c', script
+    }
+}
+```
+
+Now every time you build your app the localization files are generated from the Twine file.
+
+
+## User Interface
+
+* [Twine TextMate 2 Bundle](https://github.com/mobiata/twine.tmbundle) — This [TextMate 2](https://github.com/textmate/textmate) bundle will make it easier for you to work with Twine files. In particular, it lets you use code folding to easily collapse and expand both definitions and sections.
+* [twine_ui](https://github.com/Daij-Djan/twine_ui) — A user interface for Twine written by [Dominik Pich](https://github.com/Daij-Djan/). Consider using this if you would prefer to use Twine without dropping to a command line.
+
+## Extending Twine
+
+If there's a format Twine does not yet support and you're keen to change that, check out the [documentation](documentation/formatters.md).
+
+## Contributors
+
+Many thanks to all of the contributors to the Twine project, including:
+
+* [Blake Watters](https://github.com/blakewatters)
+* [bootstraponline](https://github.com/bootstraponline)
+* [Ishitoya Kentaro](https://github.com/kent013)
+* [Joseph Earl](https://github.com/JosephEarl)
+* [Kevin Everets](https://github.com/keverets)
+* [Kevin Wood](https://github.com/kwood)
+* [Mohammad Hejazi](https://github.com/MohammadHejazi)
+* [Robert Guo](http://www.robertguo.me/)
+* [Sebastian Ludwig](https://github.com/sebastianludwig)
+* [Sergey Pisarchik](https://github.com/SergeyPisarchik)
+* [Shai Shamir](https://github.com/pichirichi)
+
+
+[rubyzip]: http://rubygems.org/gems/rubyzip
+[git]: http://git-scm.org/
+[INI]: http://en.wikipedia.org/wiki/INI_file
+[applestrings]: http://developer.apple.com/documentation/Cocoa/Conceptual/LoadingResources/Strings/Strings.html
+[androidstrings]: http://developer.android.com/guide/topics/resources/string-resource.html
+[gettextpo]: http://www.gnu.org/savannah-checkouts/gnu/gettext/manual/html_node/PO-Files.html
+[jquerylocalize]: https://github.com/coderifous/jquery-localize
+[djangopo]: https://docs.djangoproject.com/en/dev/topics/i18n/translation/
+[tizen]: https://developer.tizen.org/documentation/articles/localization
+[printf]: https://en.wikipedia.org/wiki/Printf_format_string

data/bin/twine

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+require 'twine'
+begin
+  Twine::Runner.run(ARGV)
+rescue Twine::Error => e
+  abort e.message
+end

data/lib/twine.rb

@@ -0,0 +1,36 @@
+module Twine
+  @@stdout = STDOUT
+  @@stderr = STDERR
+
+  def self.stdout
+    @@stdout
+  end
+
+  def self.stdout=(out)
+    @@stdout = out
+  end
+
+  def self.stderr
+    @@stderr
+  end
+
+  def self.stderr=(err)
+    @@stderr = err
+  end
+
+  class Error < StandardError
+  end
+
+  require 'twine/plugin'
+  require 'twine/cli'
+  require 'twine/twine_file'
+  require 'twine/encoding'
+  require 'twine/output_processor'
+  require 'twine/placeholders'
+  require 'twine/formatters'
+  require 'twine/formatters/abstract'
+  require 'twine/formatters/android'
+  require 'twine/formatters/apple'
+  require 'twine/runner'
+  require 'twine/version'
+end

data/lib/twine/cli.rb

@@ -0,0 +1,200 @@
+require 'optparse'
+
+module Twine
+  module CLI
+    NEEDED_COMMAND_ARGUMENTS = {
+      'generate-localization-file' => 3,
+      'generate-all-localization-files' => 3,
+      'consume-localization-file' => 3,
+      'consume-all-localization-files' => 3,
+      'generate-loc-drop' => 3,
+      'consume-loc-drop' => 3,
+      'validate-twine-file' => 2
+    }
+
+    def self.parse(args)
+      options = { include: :all }
+
+      parser = OptionParser.new do |opts|
+        opts.banner = 'Usage: twine COMMAND TWINE_FILE [INPUT_OR_OUTPUT_PATH] [--lang LANG1,LANG2...] [--tags TAG1,TAG2,TAG3...] [--format FORMAT]'
+        opts.separator ''
+        opts.separator 'The purpose of this script is to convert back and forth between multiple data formats, allowing us to treat our strings (and translations) as data stored in a text file. We can then use the data file to create drops for the localization team, consume similar drops returned by the localization team, and create formatted localization files to ship with your products.'
+        opts.separator ''
+        opts.separator 'Commands:'
+        opts.separator ''
+        opts.separator '- generate-localization-file'
+        opts.separator '    Generates a localization file in a certain LANGUAGE given a particular FORMAT. This script will attempt to guess both the language and the format given the filename and extension. For example, "ko.xml" will generate a Korean language file for Android.'
+        opts.separator ''
+        opts.separator '- generate-all-localization-files'
+        opts.separator '    Generates all the localization files necessary for a given project. The parent directory to all of the locale-specific directories in your project should be specified as the INPUT_OR_OUTPUT_PATH. This command will most often be executed by your build script so that each build always contains the most recent translations.'
+        opts.separator ''
+        opts.separator '- consume-localization-file'
+        opts.separator '    Slurps all of the translations from a localization file into the specified TWINE_FILE. If you have some files returned to you by your translators you can use this command to incorporate all of their changes. This script will attempt to guess both the language and the format given the filename and extension. For example, "ja.strings" will assume that the file is a Japanese iOS strings file.'
+        opts.separator ''
+        opts.separator '- consume-all-localization-files'
+        opts.separator '    Slurps all of the translations from a directory into the specified TWINE_FILE. If you have some files returned to you by your translators you can use this command to incorporate all of their changes. This script will attempt to guess both the language and the format given the filename and extension. For example, "ja.strings" will assume that the file is a Japanese iOS strings file.'
+        opts.separator ''
+        opts.separator '- generate-loc-drop'
+        opts.separator '    Generates a zip archive of localization files in a given format. The purpose of this command is to create a very simple archive that can be handed off to a translation team. The translation team can unzip the archive, translate all of the strings in the archived files, zip everything back up, and then hand that final archive back to be consumed by the consume-loc-drop command.'
+        opts.separator ''
+        opts.separator '- consume-loc-drop'
+        opts.separator '    Consumes an archive of translated files. This archive should be in the same format as the one created by the generate-loc-drop command.'
+        opts.separator ''
+        opts.separator '- validate-twine-file'
+        opts.separator '    Validates that the given Twine file is parseable, contains no duplicates, and that no key contains invalid characters. Exits with a non-zero exit code if those criteria are not met.'
+        opts.separator ''
+        opts.separator 'General Options:'
+        opts.separator ''
+        opts.on('-l', '--lang LANGUAGES', Array, 'The language code(s) to use for the specified action.') do |l|
+          options[:languages] = l
+        end
+        opts.on('-t', '--tags TAG1,TAG2,TAG3', Array, 'The tag(s) to use for the specified action. Only definitions with ANY of the specified tags will be processed.',
+                                                      '  Specify this option multiple times to only include definitions with ALL of the specified tags. Prefix a tag',
+                                                      '  with ~ to include definitions NOT containing that tag. Omit this option to match all definitions in the Twine',
+                                                      '  data file.') do |t|
+          options[:tags] = (options[:tags] || []) << t
+        end
+        opts.on('-u', '--[no-]untagged', 'If you have specified tags using the --tags flag, then only those tags will be selected. If you also want to select',
+                                         '  all definitions that are untagged, then you can specify this option to do so.') do |u|
+          options[:untagged] = u
+        end
+        formats = Formatters.formatters.map(&:format_name).map(&:downcase)
+        opts.on('-f', '--format FORMAT', formats, "The file format to read or write: (#{formats.join(', ')}).",
+                                                  "  Additional formatters can be placed in the formats/ directory.") do |f|
+          options[:format] = f
+        end
+        opts.on('-a', '--[no-]consume-all', 'Normally, when consuming a localization file, Twine will ignore any translation keys that do not exist in your Twine file.') do |a|
+          options[:consume_all] = true
+        end
+        opts.on('-i', '--include SET', [:all, :translated, :untranslated],
+                                        "This flag will determine which definitions are included when generating localization files. It's possible values are:",
+                                        "  all: All definitions both translated and untranslated for the specified language are included. This is the default value.",
+                                        "  translated: Only definitions with translation for the specified language are included.",
+                                        "  untranslated: Only definitions without translation for the specified language are included.") do |i|
+          options[:include] = i
+        end
+        opts.on('-o', '--output-file OUTPUT_FILE', 'Write a new Twine file at this location instead of replacing the original file. This flag is only useful when',
+                                                   '  running the consume-localization-file or consume-loc-drop commands.') do |o|
+          options[:output_path] = o
+        end
+        opts.on('-n', '--file-name FILE_NAME', 'When running the generate-all-localization-files command, this flag may be used to overwrite the default file name of',
+                                               ' the format.') do |n|
+          options[:file_name] = n
+        end
+        opts.on('-r', '--[no-]create-folders', "When running the generate-all-localization-files command, this flag may be used to create output folders for all languages,",
+                                               "  if they  don't exist yet. As a result all languages will be exported, not only the ones where an output folder already",
+                                               "  exists.") do |r|
+          options[:create_folders] = r
+        end
+        opts.on('-d', '--developer-language LANG', 'When writing the Twine data file, set the specified language as the "developer language". In practice, this just',
+                                                   '  means that this language will appear first in the Twine data file. When generating files this language will be',
+                                                   '  used as default language and its translations will be used if a definition is not localized for the output language.') do |d|
+          options[:developer_language] = d
+        end
+        opts.on('-c', '--[no-]consume-comments', 'Normally, when consuming a localization file, Twine will ignore all comments in the file. With this flag set, any comments',
+                                                 '  encountered will be read and parsed into the Twine data file. This is especially useful when creating your first',
+                                                 '  Twine data file from an existing project.') do |c|
+          options[:consume_comments] = c
+        end
+        opts.on('-e', '--encoding ENCODING', 'Twine defaults to encoding all output files in UTF-8. This flag will tell Twine to use an alternate encoding for these',
+                                             '  files. For example, you could use this to write Apple .strings files in UTF-16. When reading files, Twine does its best',
+                                             "  to determine the encoding automatically. However, if the files are UTF-16 without BOM, you need to specify if it's", 
+                                             '  UTF-16LE or UTF16-BE.') do |e|
+          options[:output_encoding] = e
+        end
+        opts.on('--[no-]validate', 'Validate the Twine file before formatting it.') do |validate|
+          options[:validate] = validate
+        end
+        opts.on('-p', '--[no-]pedantic', 'When validating a Twine file, perform additional checks that go beyond pure validity (like presence of tags).') do |p|
+          options[:pedantic] = p
+        end
+        opts.on('-h', '--help', 'Show this message.') do |h|
+          puts opts.help
+          exit
+        end
+        opts.on('--version', 'Print the version number and exit.') do
+          puts "Twine version #{Twine::VERSION}"
+          exit
+        end
+        opts.separator ''
+        opts.separator 'Examples:'
+        opts.separator ''
+        opts.separator '> twine generate-localization-file twine.txt ko.xml --tags FT'
+        opts.separator '> twine generate-all-localization-files twine.txt Resources/Locales/ --tags FT,FB'
+        opts.separator '> twine consume-localization-file twine.txt ja.strings'
+        opts.separator '> twine consume-all-localization-files twine.txt Resources/Locales/ --developer-language en --tags DefaultTag1,DefaultTag2'
+        opts.separator '> twine generate-loc-drop twine.txt LocDrop5.zip --tags FT,FB --format android --lang de,en,en-GB,ja,ko'
+        opts.separator '> twine consume-loc-drop twine.txt LocDrop5.zip'
+        opts.separator '> twine validate-twine-file twine.txt'
+      end
+      begin
+        parser.parse! args
+      rescue OptionParser::ParseError => e
+        Twine::stderr.puts e.message
+        exit false
+      end
+
+      if args.length == 0
+        puts parser.help
+        exit false
+      end
+
+      # TODO: Remove this mapping of deprecated commands some time in the future - added on 31.03.
+      deprecated_command_mappings = { 
+        'generate-string-file' => 'generate-localization-file',
+        'generate-all-string-file' => 'generate-all-localization-files',
+        'consume-string-file' => 'consume-localization-file',
+        'consume-all-string-files' => 'consume-all-localization-files'
+      }
+      mapped_command = deprecated_command_mappings[args[0]]
+      if mapped_command
+        Twine::stderr.puts "WARNING: Twine commands names have changed. `#{args[0]}` is now `#{mapped_command}`. The old command is deprecated will soon stop working. For more information please check the documentation at https://github.com/mobiata/twine"
+        args[0] = mapped_command
+      end
+
+      number_of_needed_arguments = NEEDED_COMMAND_ARGUMENTS[args[0]]
+      unless number_of_needed_arguments
+        raise Twine::Error.new "Invalid command: #{args[0]}"
+      end
+      options[:command] = args[0]
+
+      if args.length < 2
+        raise Twine::Error.new 'You must specify your twine file.'
+      end
+      options[:twine_file] = args[1]
+
+      if args.length < number_of_needed_arguments
+        raise Twine::Error.new 'Not enough arguments.'
+      elsif args.length > number_of_needed_arguments
+        raise Twine::Error.new "Unknown argument: #{args[number_of_needed_arguments]}"
+      end
+
+      case options[:command]
+      when 'generate-localization-file'
+        options[:output_path] = args[2]
+        if options[:languages] and options[:languages].length > 1
+          raise Twine::Error.new 'Please only specify a single language for the generate-localization-file command.'
+        end
+      when 'generate-all-localization-files'
+        options[:output_path] = args[2]
+      when 'consume-localization-file'
+        options[:input_path] = args[2]
+        if options[:languages] and options[:languages].length > 1
+          raise Twine::Error.new 'Please only specify a single language for the consume-localization-file command.'
+        end
+      when 'consume-all-localization-files'
+        options[:input_path] = args[2]
+      when 'generate-loc-drop'
+        options[:output_path] = args[2]
+        if !options[:format]
+          raise Twine::Error.new 'You must specify a format.'
+        end
+      when 'consume-loc-drop'
+        options[:input_path] = args[2]
+      when 'validate-twine-file'
+      end
+
+      return options
+    end
+  end
+end