Tools And Library For Making It Easier To Localize Elements Created With Interface Builder


AGi18n

Utility to easily localize your iOS apps by automatically extracting texts from code and XIB files into a Localizable strings and inject them back on runtime without changing your XIB files. Check out the demo video (http://www.youtube.com/watch?v=4Cxv24W2MqA)
tools along with a library from Angel Garcia called AGi18n designed to help make it easier to localize strings within interface builder elements.
AGi18n automatically makes any strings within your interface builder elements without you needing to change any code within your apps.
There’s also a tool that makes it easy to inject your translated strings into the interface builder elements, and a library that uses some swizzling to make everything work.

You can find AGi18n on Github here. (https://github.com/angelolloqui/AGi18n)
Angel also has a nice writeup on his site comparing AGi18n with other string localization techniques.(http://angelolloqui.com/blog/28-Localization-in-iOS-apps-made-simple)

Comments

Post a Comment

Popular posts from this blog

Launch iPhone simulator without Xcode.

To launch simulator you have to way. 1. Using Terminal 2. Using UI. 1 Using UI. ->    Open Finder and then press   shift +  cmnd + g   or Go -> Go to Folder then enter this address /Applications/ Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications the double click on simulator.app. 2 Using Terminal  Open terminal and then press this command open / Applications / Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app or open `xcode-select --print-path` / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app To run application follow this, http://cocoamanifest.net/articles/2011/12/running-your-ios-app-in-the-simulator-from-the-command-line.html
Read more

How to Make REST api call in Objective-C.

We can call using this. NSString * twitterUrl = @ "YourUrlString" ; NSString * resp = [ self makeRestAPICall : twitterUrl ]; and method is -( NSString *) makeRestAPICall : ( NSString *) reqURLStr { NSURLRequest * Request = [ NSURLRequest requestWithURL :[ NSURL URLWithString : reqURLStr ]]; NSURLResponse * resp = nil ; NSError * error = nil ; NSData * response = [ NSURLConnection sendSynchronousRequest : Request returningResponse : & resp error : & error ]; NSString * responseString = [[ NSString alloc ] initWithData : response encoding : NSUTF8StringEncoding ]; NSLog (@ "%@" , responseString ); return responseString ; } 1 2 3 4 @ interface ViewController : UIViewController < NSURLConnectionDelegate > {      NSMutableData * _responseData ; }
Read more

id vs NSObject

There's often confusion about the difference between the following three declarations in Objective-C: id foo1; ->   It simply declares a pointer to some Objective-C object,  If you don't want (or can't have) any type checking, then use   id . if you do want compile-time type checking, you must decide between the second and third cases.. NSObject *foo2; ->  declaring a generic pointer of type NSObject* id<NSObject> foo3; ->   pointer to  any  object that behaves like an NSObjec , "foo3 is a pointer to an object of any type that behaves like an NSObject" , ( you really don't care what class the object is, you only care that it  behaves  like an NSObject.) The first one is the most common. It simply declares a pointer to some Objective-C object (see  /usr/include/objc/objc.h ).  id  gives the compiler no information about the actual type of the object, so the compiler cannot do compile-time type ...
Read more