The format of the stringsdict file looks like this.
We’re also introducing NSString Variable Width Rule Type.… In OS X 10.11 and i OS 9.0 NSNotification Center and NSDistributed Notification Center will no longer send notifications to registered observers that may be deallocated.
If the observer is able to be stored as a zeroing-weak reference the underlying storage will store the observer as a zeroing weak reference, alternatively if the object cannot be stored weakly (i.e.
it has a custom retain/release mechanism that would prevent the runtime from being able to store the object weakly) it will store the object as a non-weak zeroing reference.
The width is just an integer identifying one of the variations.
The strings are sorted such that if the width does not exist, the string at the next smaller width is returned or the smallest available if none are smaller.
The application can decide on their own contexts, but i OS uses em’s; the number of ‘M' characters for the current system-font that will fit the width of the window.
For others, it may be too long and it’d be desirable to shorten it to something like “Welcome." Our solution is to allow developers/localizers to provide different width-variations for a string in a stringsdict file, the same file meant for different cardinalities (“1 file is selected” vs. The -[NSBundle localized String For Key:value:table:] method reads the stringsdict file and creates an NSString that knows about the different variations.We have a single method, variant Fitting Presentation Width: on NSString.It selects the appropriate variation for the given width.NSProgress now supports composition of progress objects into trees both implicitly and explicitly.The implicit approach uses the existing API, such as -become Current With Pending Unit Count: and -resign Current.