organicmaps/twine
Archived
13
Fork 0
Code Issues 1 Pull requests 2 Projects Releases Wiki Activity Actions

Fix minor README issues.

Browse source
This commit is contained in:
Sebastian Celis 2012-04-13 11:25:04 -05:00
parent b886d78198
commit bb0b51a07a
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -115,7 +115,7 @@ This command gives you useful information about your strings. It will tell you h
$ twine generate-report /path/to/strings.txt
## Twine in your Build Process
## Twine and Your Build Process
It is easy to incorporate Twine right into your iOS and Mac OS X app build processes.
@ -124,14 +124,14 @@ It is easy to incorporate Twine right into your iOS and Mac OS X app build proce
$ twine generate-all-string-files strings.txt Resources/Locales/ --tags tag1,tag2
Make sure you point Twine at your strings data file, the directory that contains all of your `.lproj` directories, and and the tags that describe the strings you want to use for this project.
Make sure you point Twine at your strings data file, the directory that contains all of your `.lproj` directories, and the tags that describe the strings you want to use for this project.
3. Drag the `Resources/Locales/` directory to the Xcode project navigator so that Xcode knows to include all of these strings files in your build.
4. In Xcode, navigate to the "Build Phases" tab of your target.
5. Click on the "Add Build Phase" button and select "Add Run Script".
6. Drag the new "Run Script" build phase up so that it runs earlier in the build process. It doesn't really matter where, as long as it happens before the resources are copied to your bundle.
7. Edit your script to run the exact same command you ran in step (2) above.
Now, whenever you build your application, Xcode will automatically invoke Twine to make sure that your `.strings` files are always up-to-date.
Now, whenever you build your application, Xcode will automatically invoke Twine to make sure that your `.strings` files are up-to-date.
[rubyzip]: http://rubygems.org/gems/rubyzip
[git]: http://git-scm.org/