ad_localize 4.0.7 → 4.0.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7c430461018f65ed97a0eee0978989c7f051df7228dccede2282417cfd70b837
-  data.tar.gz: 38b0d8ddbd9493e3d1ba4d483bc28f943141cc7f60f4bd5d3812a5a2c715ff17
+  metadata.gz: 0c46c9d2fd0ef0b980ac43804c9f063d52b36be6083de7193c3e65dde9447030
+  data.tar.gz: 3a6eac4fe189d7e6de30220b410f0331d8b3a3a90a72c970a9e7ee4aa727c67c
 SHA512:
-  metadata.gz: 18b47316425537c6bc79f9b1db9eb828a82d380dcab2f90eb8e9ba17875e03d5cdcd4d1024f99a813090a0c477b728991fc7c94751df8bb58f3455d2d4813884
-  data.tar.gz: e96d73dde24bec5f84951fb880a6a1809256ab3581e51d9fc68b3e5bd9011ffb50d2173ebf5ef0ac80b8ff89387c4d2a98d6817ac799a5f58234d37948cee053
+  metadata.gz: 59fcc792844bf2558f2323f99de099709bae2145ae399231509855230268dd85756cc85145d38b5bdceb908b10635d59f6a2a7067ba32de51bae754c1e99af4a
+  data.tar.gz: 795f9239b4548412ba8f251d6328c5240d387e6089fa389e0d9c4581673dd40eb3dbc7808cc0c07b3cc8fe2c4935cc427d9c51b689bc57fb897b9b01bf8f77a6

data/CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.0.8] - 2021-05-25
+### Fixed
+- Add `NFCReaderUsageDescription` to InfoPlist keys for iOS
+
 ## [4.0.7] - 2021-05-18
 ### Changed
 - Support Ruby 3.x
@@ -15,12 +19,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [4.0.5] - 2020-11-12
 ### Fixed
   - Fix csv file type check (also add compatibility with macOS Big Sur)
-  
+
 ## [4.0.4] - 2020-11-09
 ### Fixed
   - Fix android special character escaping [#56](https://github.com/applidium/ad_localize/issues/56)
   - Fix platform filter on export [#55](https://github.com/applidium/ad_localize/issues/55)
-  
+
 ### Changed
   - Use default terminal color for debug log
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    ad_localize (4.0.7)
+    ad_localize (4.0.8)
       activesupport (>= 6.1.3.2, < 7.0)
       colorize (~> 0.8)
       google-api-client (~> 0.34)
@@ -26,12 +26,16 @@ GEM
     concurrent-ruby (1.1.8)
     declarative (0.0.20)
     diffy (3.3.0)
-    faraday (1.4.1)
+    faraday (1.4.2)
+      faraday-em_http (~> 1.0)
+      faraday-em_synchrony (~> 1.0)
       faraday-excon (~> 1.1)
       faraday-net_http (~> 1.0)
       faraday-net_http_persistent (~> 1.1)
       multipart-post (>= 1.2, < 3)
       ruby2_keywords (>= 0.0.4)
+    faraday-em_http (1.0.0)
+    faraday-em_synchrony (1.0.0)
     faraday-excon (1.1.0)
     faraday-net_http (1.0.1)
     faraday-net_http_persistent (1.1.0)
@@ -49,7 +53,7 @@ GEM
       rexml
       signet (~> 0.14)
       webrick
-    google-apis-discovery_v1 (0.2.0)
+    google-apis-discovery_v1 (0.4.0)
       google-apis-core (~> 0.1)
     google-apis-generator (0.2.0)
       activesupport (>= 5.0)
@@ -79,7 +83,7 @@ GEM
       ruby-progressbar
     multi_json (1.15.0)
     multipart-post (2.1.1)
-    nokogiri (1.11.4)
+    nokogiri (1.11.5)
       mini_portile2 (~> 2.5.0)
       racc (~> 1.4)
     os (1.1.1)

data/README.md

@@ -2,7 +2,7 @@
 
 The purpose of this gem is to automatically generate wording files from a CSV input (CSV file or Google Spreadsheet).
 It supports iOS, Android, JSON, YAML and Java Properties.
-It is a useful tool when working on a mobile application or a SPA.  
+It is a useful tool when working on a mobile application or a SPA.
 
 ## Installation
 
@@ -41,12 +41,12 @@ $ ad_localize -k <your-spreadsheet-drive-key>
 $ ad_localize -k <your-spreadsheet-drive-key> -s <comma-separated-sheet-id-list>
 ```
 
-* Export wording from a private google spreadsheet. It requires a [Google Cloud Service Account](#using-a-google-cloud-service-account). 
+* Export wording from a private google spreadsheet. It requires a [Google Cloud Service Account](#using-a-google-cloud-service-account).
 ```
 $ GCLOUD_CLIENT_SECRET=$(cat <path-to-client-secret.json>) ad_localize -k <your-spreadsheet-drive-key>
 ```
 
-* Export wording from all sheets in a google spreadsheet. It requires a [Google Cloud Service Account](#using-a-google-cloud-service-account). 
+* Export wording from all sheets in a google spreadsheet. It requires a [Google Cloud Service Account](#using-a-google-cloud-service-account).
 ```
 $ GCLOUD_CLIENT_SECRET=$(cat <path-to-client-secret.json>) ad_localize -k <your-spreadsheet-drive-key> -e
 ```
@@ -76,7 +76,7 @@ If you want more examples, please open a documentation issue.
     require 'ad_localize'
     # create optional google spreasheet options
     g_spreadsheet_options = AdLocalize::Requests::GSpreadsheetOptions.new(spreadsheet_id: 'some_id', sheet_ids: ['first', 'second'], service_account_config: ENV['GCLOUD_CLIENT_SECRET'])
-    # create export request    
+    # create export request
     export_request = AdLocalize::Requests::ExportRequest.new(g_spreadsheet_options: g_spreadsheet_options, verbose: true)
     # execute request
     AdLocalize::Interactors::ExecuteExportRequest.new.call(export_request: export_request)
@@ -86,20 +86,20 @@ If you want more examples, please open a documentation issue.
 ### Share to anyone with the link
 
 If you do not have high security concerns, the simplest way to access a google spreadsheet is to allow **anyone** with the link to **view** it and enable the `Viewers and commenters can see the option to download, print, and copy` option in the spreadsheet sharing settings.
-    
+
 ### Use a Google Cloud Service Account
 
-To use a private google spreasheet you need to use a Google Cloud Service Account. Here are the steps to follow :    
-1. Create a GCloud Service Account:    
-    - Go to [Google Cloud Console](https://console.cloud.google.com/)  
-    - Either create a new project or use an existing one (when using Firebase, a GCloud project is created)  
-    - Go to *IAM & Admin / Service Account* and create a new service account.  
-    - Store the created `client-secret.json` (in a password manager for example)  
-2. Enable Google Spreadsheet API for the project  
-    - Go to *API / Library* and enable the **Google Spreadsheet API** there.  
-3. Add the service account to a spreadsheet.  
+To use a private google spreasheet you need to use a Google Cloud Service Account. Here are the steps to follow :
+1. Create a GCloud Service Account:
+    - Go to [Google Cloud Console](https://console.cloud.google.com/)
+    - Either create a new project or use an existing one (when using Firebase, a GCloud project is created)
+    - Go to *IAM & Admin / Service Account* and create a new service account.
+    - Store the created `client-secret.json` (in a password manager for example)
+2. Enable Google Spreadsheet API for the project
+    - Go to *API / Library* and enable the **Google Spreadsheet API** there.
+3. Add the service account to a spreadsheet.
     - In *IAM & Admin / Service Account*, the service account's email is listed. Invite it to the spreadsheet to export.
-      
+
 ```
 $ GCLOUD_CLIENT_SECRET=$(cat <path-to-client-secrets>) ad_localize -k # one way
 $ GCLOUD_CLIENT_SECRET=$(cat <path-to-client-secrets>) ad_localize -k <your-spreadsheet-drive-key> -s <comma-separated-sheet-id-list> # another way
@@ -124,11 +124,11 @@ $ ad_localize -k <your-spreadsheet-drive-key> -s <comma-separated-sheet-id-list>
 - Keys should contain only letter, number, underscore and dot : [a-z0-9_.]+.
 - Format specifiers must be numeroted if there are more than one in a translation string (eg: `"%1$@ %2$@'s report"`).
 
-### Comments 
+### Comments
 
 _Only for Android and iOS_
 
-To add comments for iOS or Android, simply add a comment column using the naming convention `comment <locale>`.  
+To add comments for iOS or Android, simply add a comment column using the naming convention `comment <locale>`.
 Comments are available in `strings.xml`, `Localizable.strings`, `Localizable.stringsdict`, `InfoPlist.strings`. Here is an example for `InfoPlist.strings` :
 
 | key | en | comment en |
@@ -177,21 +177,22 @@ _Only for iOS._
 
 Every key that matches the following formats will be added to the `InfoPlist.strings` file instead of `Localizable.strings`:
 * `NS...UsageDescription`
+* `NFCReaderUsageDescription`
 * `CF...Name`
 
 ### Nested wording
 
 _Only for YAML and JSON_
 
-For these two platforms it is common to have nested wording files, either to handle plural or to group wording by sections. To handle this behavior in a simple way you should use dots in the key to separate the different levels. For example :  
- 
+For these two platforms it is common to have nested wording files, either to handle plural or to group wording by sections. To handle this behavior in a simple way you should use dots in the key to separate the different levels. For example :
+
 | key | fr |
 | --- | --- |
 | login.password | mot de passe |
 | login.email | email |
 
 ```json
-{"login":{"password":"mot de passe","email":"email"}} 
+{"login":{"password":"mot de passe","email":"email"}}
 ```
 
 ```yaml
@@ -199,14 +200,14 @@ fr:
   login:
     password: "mot de passe"
     email: "email"
-```  
+```
 
 
 ## Output
 
-The default output folder name is `exports`.  
-If your export is for multiple platforms there will be an intermediate folder for each platform, otherwise the wording files (and folders) will directly be generated in the export folder.  
-Any existing file will be overriden. 
+The default output folder name is `exports`.
+If your export is for multiple platforms there will be an intermediate folder for each platform, otherwise the wording files (and folders) will directly be generated in the export folder.
+Any existing file will be overriden.
 You can see examples of generated files in `test/fixtures/export_references/`
 
 Here an export tree example for all supported platforms in `fr` and `en`:

data/lib/ad_localize/entities/key.rb

@@ -4,7 +4,7 @@ module AdLocalize
       PLURAL_KEY_REGEXP = /\#\#\{([A-Za-z]+)\}/.freeze
       ADAPTIVE_KEY_REGEXP = /\#\#\{(\d+)\}/.freeze
       # see https://developer.apple.com/documentation/bundleresources/information_property_list
-      INFO_PLIST_KEY_REGEXP = /(NS.+UsageDescription)|(CF.+Name)/.freeze
+      INFO_PLIST_KEY_REGEXP = /(NS.+UsageDescription)|(CF.+Name)|NFCReaderUsageDescription/.freeze
 
       def initialize(label:)
         @label = label

data/lib/ad_localize/version.rb

@@ -1,3 +1,3 @@
 module AdLocalize
-  VERSION = "4.0.7"
+  VERSION = "4.0.8"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ad_localize
 version: !ruby/object:Gem::Version
-  version: 4.0.7
+  version: 4.0.8
 platform: ruby
 authors:
 - Edouard Siegel
@@ -17,7 +17,7 @@ authors:
 - Claire Dufetrelle
 - Pierre Felgines
 - Satyan Jacquens
-autorequire:
+autorequire: 
 bindir: exe
 cert_chain: []
 date: 2018-04-18 00:00:00.000000000 Z
@@ -268,7 +268,7 @@ homepage: https://github.com/applidium/ad_localize
 licenses:
 - MIT
 metadata: {}
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -283,8 +283,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.15
-signing_key:
+rubygems_version: 3.0.3
+signing_key: 
 specification_version: 4
 summary: AdLocalize helps with mobile and web applications wording
 test_files: []