country-select-engine 0.1.0

data/script/google.zh-TW.yml

@@ -0,0 +1,143 @@
+timezones:
+- 國際日期變更線以西
+- 中途島
+- 薩摩亞
+- 夏威夷
+- 阿拉斯加
+- 太平洋時間（美國和加拿大）
+- 蒂華納
+- 山地時間（美國和加拿大）
+- 亞利桑那州
+- 奇瓦瓦
+- 馬薩特蘭
+- 中部時間（美國和加拿大）
+- 薩斯喀徹溫省
+- 瓜達拉哈拉
+- 墨西哥城
+- 蒙特雷
+- 中美洲
+- 東部時間（美國和加拿大）
+- 印地安那（東）
+- 波哥大
+- 利馬
+- 基多
+- 大西洋時間（加拿大）
+- 加拉加斯
+- 拉巴斯
+- 聖地亞哥
+- 紐芬蘭
+- 巴西利亞
+- 布宜諾斯艾利斯
+- 喬治敦
+- 格陵蘭
+- 大西洋中部
+- 亞速爾群島
+- 佛得角。
+- 都柏林
+- 愛丁堡
+- 里斯本
+- 倫敦
+- 卡薩布蘭卡
+- 蒙羅維亞
+- UTC
+- 貝爾格萊德
+- 布拉迪斯拉發
+- 布達佩斯
+- 盧布爾雅那
+- 布拉格
+- 薩拉熱窩
+- 斯科普里
+- 華沙
+- 薩格勒布
+- 布魯塞爾
+- 哥本哈根
+- 馬德里
+- 巴黎
+- 阿姆斯特丹
+- 柏林
+- 伯爾尼
+- 羅馬
+- 斯德哥爾摩
+- 維也納
+- 西中部非洲
+- 布加勒斯特
+- 開羅
+- 赫爾辛基
+- Kyev
+- 裡加
+- 索非亞
+- 塔林
+- 維爾紐斯
+- 雅典
+- 伊斯坦布爾
+- 明斯克
+- 耶路撒冷
+- 哈拉雷
+- 比勒陀利亞
+- 莫斯科
+- 聖彼得堡
+- 伏爾加格勒
+- 科威特
+- 利雅得
+- 內羅畢
+- 巴格達
+- 德黑蘭
+- 阿布扎比
+- 馬斯喀特
+- 巴庫
+- 第比利斯
+- 埃里溫
+- 喀布爾
+- 葉卡捷琳堡
+- 伊斯蘭堡
+- 卡拉奇
+- 塔什幹
+- 奈
+- 加爾各答
+- 孟買
+- 新德里
+- 加德滿都
+- 阿斯塔納
+- 達卡
+- 斯里蘭卡Jayawardenepura
+- 阿拉木圖
+- 新西伯利亞
+- 仰光
+- 曼谷
+- 河內
+- 雅加達
+- 克拉斯諾亞爾斯克
+- 北京
+- 重慶
+- 香港
+- 烏魯木齊
+- 吉隆坡
+- 新加坡
+- 台北
+- 珀斯
+- 伊爾庫茨克
+- 烏蘭Bataar
+- 首爾
+- 大阪
+- 札幌
+- 東京
+- 雅庫茨克
+- 達爾文
+- 阿德萊德
+- 堪培拉
+- 墨爾本
+- 悉尼
+- 布里斯班
+- 霍巴特
+- 符拉迪沃斯托克
+- 關島
+- 莫爾茲比港
+- 馬加丹
+- 所羅門
+- 新喀裡多尼亞
+- 斐濟
+- 堪察加
+- 馬歇爾
+- 奧克蘭
+- 惠靈頓
+- 努庫阿洛法

data/script/rails

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+# This command will automatically be run when you run "rails" with Rails 3 gems installed from the root of your application.
+
+ENGINE_ROOT = File.expand_path('../..', __FILE__)
+ENGINE_PATH = File.expand_path('../../lib/country-select-engine/engine', __FILE__)
+
+require 'rails/all'
+require 'rails/engine/commands'

data/script/timezones.yml

@@ -0,0 +1,144 @@
+en:
+  timezones:
+    International Date Line West: International Date Line West
+    Midway Island: Midway Island
+    Samoa: Samoa
+    Hawaii: Hawaii
+    Alaska: Alaska
+    Pacific Time (US & Canada): Pacific Time (US & Canada)
+    Tijuana: Tijuana
+    Mountain Time (US & Canada): Mountain Time (US & Canada)
+    Arizona: Arizona
+    Chihuahua: Chihuahua
+    Mazatlan: Mazatlan
+    Central Time (US & Canada): Central Time (US & Canada)
+    Saskatchewan: Saskatchewan
+    Guadalajara: Guadalajara
+    Mexico City: Mexico City
+    Monterrey: Monterrey
+    Central America: Central America
+    Eastern Time (US & Canada): Eastern Time (US & Canada)
+    Indiana (East): Indiana (East)
+    Bogota: Bogota
+    Lima: Lima
+    Quito: Quito
+    Atlantic Time (Canada): Atlantic Time (Canada)
+    Caracas: Caracas
+    La Paz: La Paz
+    Santiago: Santiago
+    Newfoundland: Newfoundland
+    Brasilia: Brasilia
+    Buenos Aires: Buenos Aires
+    Georgetown: Georgetown
+    Greenland: Greenland
+    Mid-Atlantic: Mid-Atlantic
+    Azores: Azores
+    Cape Verde Is.: Cape Verde Is.
+    Dublin: Dublin
+    Edinburgh: Edinburgh
+    Lisbon: Lisbon
+    London: London
+    Casablanca: Casablanca
+    Monrovia: Monrovia
+    UTC: UTC
+    Belgrade: Belgrade
+    Bratislava: Bratislava
+    Budapest: Budapest
+    Ljubljana: Ljubljana
+    Prague: Prague
+    Sarajevo: Sarajevo
+    Skopje: Skopje
+    Warsaw: Warsaw
+    Zagreb: Zagreb
+    Brussels: Brussels
+    Copenhagen: Copenhagen
+    Madrid: Madrid
+    Paris: Paris
+    Amsterdam: Amsterdam
+    Berlin: Berlin
+    Bern: Bern
+    Rome: Rome
+    Stockholm: Stockholm
+    Vienna: Vienna
+    West Central Africa: West Central Africa
+    Bucharest: Bucharest
+    Cairo: Cairo
+    Helsinki: Helsinki
+    Kyev: Kyev
+    Riga: Riga
+    Sofia: Sofia
+    Tallinn: Tallinn
+    Vilnius: Vilnius
+    Athens: Athens
+    Istanbul: Istanbul
+    Minsk: Minsk
+    Jerusalem: Jerusalem
+    Harare: Harare
+    Pretoria: Pretoria
+    Moscow: Moscow
+    St. Petersburg: St. Petersburg
+    Volgograd: Volgograd
+    Kuwait: Kuwait
+    Riyadh: Riyadh
+    Nairobi: Nairobi
+    Baghdad: Baghdad
+    Tehran: Tehran
+    Abu Dhabi: Abu Dhabi
+    Muscat: Muscat
+    Baku: Baku
+    Tbilisi: Tbilisi
+    Yerevan: Yerevan
+    Kabul: Kabul
+    Ekaterinburg: Ekaterinburg
+    Islamabad: Islamabad
+    Karachi: Karachi
+    Tashkent: Tashkent
+    Chennai: Chennai
+    Kolkata: Kolkata
+    Mumbai: Mumbai
+    New Delhi: New Delhi
+    Kathmandu: Kathmandu
+    Astana: Astana
+    Dhaka: Dhaka
+    Sri Jayawardenepura: Sri Jayawardenepura
+    Almaty: Almaty
+    Novosibirsk: Novosibirsk
+    Rangoon: Rangoon
+    Bangkok: Bangkok
+    Hanoi: Hanoi
+    Jakarta: Jakarta
+    Krasnoyarsk: Krasnoyarsk
+    Beijing: Beijing
+    Chongqing: Chongqing
+    Hong Kong: Hong Kong
+    Urumqi: Urumqi
+    Kuala Lumpur: Kuala Lumpur
+    Singapore: Singapore
+    Taipei: Taipei
+    Perth: Perth
+    Irkutsk: Irkutsk
+    Ulaan Bataar: Ulaan Bataar
+    Seoul: Seoul
+    Osaka: Osaka
+    Sapporo: Sapporo
+    Tokyo: Tokyo
+    Yakutsk: Yakutsk
+    Darwin: Darwin
+    Adelaide: Adelaide
+    Canberra: Canberra
+    Melbourne: Melbourne
+    Sydney: Sydney
+    Brisbane: Brisbane
+    Hobart: Hobart
+    Vladivostok: Vladivostok
+    Guam: Guam
+    Port Moresby: Port Moresby
+    Magadan: Magadan
+    Solomon Is.: Solomon Is.
+    New Caledonia: New Caledonia
+    Fiji: Fiji
+    Kamchatka: Kamchatka
+    Marshall Is.: Marshall Is.
+    Auckland: Auckland
+    Wellington: Wellington
+    Nuku'alofa: Nuku'alofa

data/script/translate_timezones.rb

@@ -0,0 +1,26 @@
+require 'yaml'
+
+# copy 'google.yml' to google translate 
+# and save the result into google.locale.yml
+
+output_path = 'config/locales/' # must be created
+
+locales = ['ru', 'zh-CN']
+
+locales.each do |locale|
+  template = YAML::load(File.open("script/google.yml"))
+  translation = YAML::load(File.open("script/google.#{locale}.yml"))
+  languages = Hash.new
+  template['timezones'].each_with_index do |x, i|
+    languages[x] = translation.first[1][i]
+    puts "#{x} ==> #{languages[x]}"
+  end
+  output = {locale => {'timezones' => languages}}
+  o = output_path+'timezones.'+locale+'.yml'
+  puts "write #{o}"
+  s = YAML.dump(output)
+  s = s.lines.to_a[1..-1].join
+  f = File.open(o, 'w')
+  f.write(s)
+  f.close
+end

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.

data/spec/dummy/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+Dummy::Application.load_tasks

data/spec/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,16 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require chosen.jquery.min
+//= require_tree .

data/spec/dummy/app/assets/javascripts/dummy.js

@@ -0,0 +1,2 @@
+// Place all the behaviors and hooks related to the matching controller here.
+// All this logic will automatically be available in application.js.

data/spec/dummy/app/assets/stylesheets/application.css

@@ -0,0 +1,14 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require chosen
+ *= require_tree .
+*/

data/spec/dummy/app/assets/stylesheets/dummy.css

@@ -0,0 +1,4 @@
+/*
+  Place all the styles related to the matching controller here.
+  They will automatically be included in application.css.
+*/

data/spec/dummy/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/spec/dummy/app/controllers/dummy_controller.rb

@@ -0,0 +1,4 @@
+class DummyController < ApplicationController
+  def index
+  end
+end

data/spec/dummy/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/spec/dummy/app/helpers/dummy_helper.rb

@@ -0,0 +1,2 @@
+module DummyHelper
+end