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

Info.plist localization #13

Open
fklebert opened this issue Nov 12, 2020 · 3 comments
Open

Info.plist localization #13

fklebert opened this issue Nov 12, 2020 · 3 comments

Comments

@fklebert
Copy link

We are using your macro and really like it. 👍
One question: Is there a way to add localization for Info.plist. That means providing InfoPlist.strings files in their respective subdirectories in a similar way as it works with the Info.plist.in?
Is this something I have overseen, or is it simply not implemented?

@OlivierLDff
Copy link
Owner

I haven't look to localization for now so i don't really know how it work.
I want the function to stay simple and generic. If you have a good idea on how localization API should look feel free to PR and we will discuss.
There are so many things that can be added to Info.plist that a function can't implement them all.
The idea is for you to copy Info.plist.in in your sources, and give it to the function with CUSTOM_PLIST argument.
Then edit Info.plist.in with your additional entries.

@fklebert
Copy link
Author

Just to give you some feedback: We have tried for quite some time to solve the localization issue, but in the end decided to do it manually in the generated XCode project. It is simply a couple of clicks and not worth the effort of writing a python script that manipulates the Xcode project file, since this seems the approach most people use.
Please feel free to close the issue if you do not want to invest huge amount of time in researching.. ;-)

@OlivierLDff
Copy link
Owner

OlivierLDff commented Dec 11, 2020

Ok that sound quite annoying to do.
I will see if i come up with good solution for that in the future. I keep you updated.
Thank for the update.
I keep the issue opened, at least for people trying to do the same.

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

No branches or pull requests

2 participants