prepare submission

DESCRIPTION

@@ -17,7 +17,8 @@ Suggests:
     tibble,
     purrrlyr,
     knitr,
-    rmarkdown
+    rmarkdown,
+    magrittr
 URL: https://github.com/Tazinho/snakecase
 BugReports: https://github.com/Tazinho/snakecase/issues
 Encoding: UTF-8

NEWS.md

@@ -5,7 +5,7 @@
 New functionality:
 
 * **abbreviations**: Abbreviations are now ...
-  * ... matched case-insensitive inside of groups of conneceted lower/upper case sequences.
+  * ... matched case-insensitive inside of groups of connected lower/upper case sequences.
   * ... consistently formatted according to the supplied case.
   * ... formatted exactly as supplied for the cases title, mixed, lower and upper camel.
   * ... protected from the parsing. This means that 
@@ -24,9 +24,11 @@ Infrastructure:
 
 * **CII best practices badge**: Achieved the criteria for the best practices badge. Current status is under https://bestpractices.coreinfrastructure.org/de/projects/2475  
 * **R Version**: Increase from 3.1 to 3.2 regarding the usage of `tools::toTitleCase()` inside `to_title_case()`.  
-* **Tests**: Skip `to_any_case()` tests (janitor-pkg-tests, transliterations and complex strings) when platform charset is not UTF-8 to resolve CRAN notification regarding character encoding.  
 * **Vignettes**: The blog article "Introducing the snakecase package" was added as a vignette.  
 * **Documentation**: The readme, the examples and the function documentation were updated according to the new functionality.
+* **Resolve CRAN notes**:
+  * **Tests**: Skip `to_any_case()` tests (janitor-pkg-tests, transliterations and complex strings) when platform charset is not UTF-8 to resolve CRAN notification regarding character encoding.
+  * **Vignettes**: Build the package with new version of knitr to resolve CRAN notification regarding vignette encoding.
 
 # snakecase 0.10.0.9000
 
@@ -60,7 +62,7 @@ Infrastructure:
 
 * **cases**: added `to_sentence_case()` (same as snake, but first letter is uppercase and default sep_out is space).
 * **numerals**: added `numerals` argument to all caseconverters including `to_any_case()` to format the alignment of digits (`middle`, `left`,`right`, `asis`). Therefore `parsing_option` nr 4 might be removed in later releases, as it is the same as `parsing_option = 1` and `numerals = "asis"`.
-* **transliterations**: When named character elements are supplied as part of `transliterations`, anything that mathches the name is replaced by the corresponding value.
+* **transliterations**: When named character elements are supplied as part of `transliterations`, anything that matches the name is replaced by the corresponding value.
 * attributes are now preserved (not only names as before)
 
 # snakecase 0.9.1
@@ -343,7 +345,7 @@ for whitespaces in output postprocess = " " is recommended.
 * introduced `to_screaming_snake_case()`
 * added arguments prefix, postfix and replace_special_characters to `to_any_case()`.
 * completely renewed readme
-* updated tests and highly modularized all tests. (just to_any_case lacks some tests now and in general more examples testcases have to be written)
+* updated tests and highly modularized all tests. (just to_any_case lacks some tests now and in general more examples test cases have to be written)
 
 # snakecase 0.2.2
 
@@ -363,7 +365,7 @@ the old name before, since the package was in early dev-stage anyway).
 * started a to develop and implement consistent logic (which still has to be better documented in the readme)
 * introduced tests for more hard coded examples and the logic behind it (still more
 hardcoded examples and a third part of the logic have to be tested)
-* internal logic has been simplified and modularised a lot, which makes it easier
+* internal logic has been simplified and modularized a lot, which makes it easier
 to maintain and introduce more high-level features in the future
 * added integrated tests via AppVeyor on windows
 * added badges for cran status and code coverage to readme

README.Rmd

@@ -121,7 +121,7 @@ to_snake_case(c("HHcity", "IDtable1", "KEYtable2", "newUSelections"),
               parsing_option = 3)
 ```
 
-To suppress conversion after a non-alphanumeric characters (except `"_"`), you can add a minus infront of the `parsing_option`, e.g.:
+To suppress conversion after a non-alphanumeric characters (except `"_"`), you can add a minus in front of the `parsing_option`, e.g.:
 
 ```{r, collapse = TRUE}
 to_upper_camel_case("look_AfterThe-hyphen andThe.dot",
@@ -131,7 +131,7 @@ to_upper_camel_case("look_AfterThe-hyphen andThe.dot",
 
 And to suppress the parsing set `parsing_option = 0`.
 
-If you are interested in the implementaion of a specific `parsing_option`, please open an issue.
+If you are interested in the implementation of a specific `parsing_option`, please open an issue.
 
 ### Conversion
 

README.md

@@ -171,7 +171,7 @@ to_snake_case(c("HHcity", "IDtable1", "KEYtable2", "newUSelections"),
 ```
 
 To suppress conversion after a non-alphanumeric characters (except
-`"_"`), you can add a minus infront of the `parsing_option`, e.g.:
+`"_"`), you can add a minus in front of the `parsing_option`, e.g.:
 
 ``` r
 to_upper_camel_case("look_AfterThe-hyphen andThe.dot",
@@ -182,7 +182,7 @@ to_upper_camel_case("look_AfterThe-hyphen andThe.dot",
 
 And to suppress the parsing set `parsing_option = 0`.
 
-If you are interested in the implementaion of a specific
+If you are interested in the implementation of a specific
 `parsing_option`, please open an issue.
 
 ### Conversion

cran-comments.md

@@ -8,11 +8,7 @@
 * win-builder: old, release, devel  
 
 ## R CMD check results
-There were no ERRORs or WARNINGs.
-
-NOTEs:  
-* For win-builder release (R3.6): "Found the following hidden files and directories: .github. These were most likely included in error. See section 'Package structure' in the 'Writing R Extensions' manual."  
-I added the line "^\.github$" to .Rbuildignore, but for some reason this doesn't always resolve this on the win-builder builds.
+There were no ERRORs, WARNINGs or NOTEs.
 
 ## Downstream dependencies
 No ERRORs or WARNINGs found.