Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use modern localization identifier 'en' for the development region #669

Merged
merged 1 commit into from
Apr 16, 2019

Conversation

HeEAaD
Copy link
Contributor

@HeEAaD HeEAaD commented Mar 27, 2019

Change default development_region from "English" to "en" because "English" is deprecated.

Issue

From the Xcode 10.2 release notes:

Xcode now more carefully distinguishes between legacy localization identifiers such as “English” and modern localization identifiers such as “en” and represents them both in both project files and the user interface. (45469882)

https://developer.apple.com/documentation/xcode_release_notes/xcode_10_2_release_notes?language=objc#3136790

This leads to deprecation warnings in Xcode 10.2:

Migrating the English, deprecated localization to English is recommended for all projects. This will ensure localized resources are placed in “en.lproj” directories instead of deprecated “English.lproj” directories.

@amorde amorde requested a review from segiddins April 13, 2019 03:18
@amorde
Copy link
Member

amorde commented Apr 13, 2019

LGTM but would like 1 more review.

I've experienced this in my own projects as well

@amorde amorde merged commit 45e59e6 into CocoaPods:master Apr 16, 2019
@amorde
Copy link
Member

amorde commented Apr 16, 2019

Thanks @HeEAaD!

@@ -15,6 +15,9 @@
* Normalize xcconfig path when generating includes.
[bclymer](https://github.com/bclymer)

* Use modern localization identifier 'en' for the development region.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change log entry was not rebased to latest master it now appears as if it was in 1.8.2 will fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants