Strings File - Revision history

Jsummers: Category:Resources

2016-04-30T14:41:22Z

Category:Resources

Dan Tobias at 22:31, 16 March 2016

2016-03-16T22:31:51Z

Dan Tobias at 23:17, 4 February 2013

2013-02-04T23:17:27Z

Dan Tobias at 03:42, 3 February 2013

2013-02-03T03:42:16Z

Dan Tobias at 15:49, 21 January 2013

2013-01-21T15:49:57Z

Dan Tobias at 14:33, 21 January 2013

2013-01-21T14:33:00Z

Dan Tobias at 06:28, 21 January 2013

2013-01-21T06:28:12Z

Dan Tobias at 06:27, 21 January 2013

2013-01-21T06:27:58Z

Dan Tobias at 05:13, 21 January 2013

2013-01-21T05:13:11Z

Dan Tobias at 04:05, 21 January 2013

2013-01-21T04:05:46Z

← Older revision		Revision as of 14:41, 30 April 2016
Line 33:		Line 33:
	[[Category:iOS]]		[[Category:iOS]]
	[[Category:Development]]		[[Category:Development]]
		+	[[Category:Resources]]

← Older revision		Revision as of 22:31, 16 March 2016
Line 32:		Line 32:
	[[Category:Macintosh]]		[[Category:Macintosh]]
	[[Category:iOS]]		[[Category:iOS]]
		+	[[Category:Development]]

@@ Line 24: / Line 24: @@
 Within iOS apps, the structure and filenames are similar, but the format is [[Property List/Binary]].
-When you are building a project for either an OS X or iOS app in Xcode, the editing of .strings files is done in [[UTF-8]] in the native name/value format described above; the files are then converted to the appropriate format for the target platform when the app is built.
+When you are building a project for either an OS X or iOS app in Xcode, the editing of .strings files is done in [[UTF-8]] in the native name/value format described above (at least in the default configuration; this is configurable to other character encodings and to the different line-break conventions of CR, LF, or CRLF); the files are then converted to the appropriate format for the target platform when the app is built.
 == References ==

← Older revision		Revision as of 03:42, 3 February 2013
Line 31:		Line 31:

	[[Category:Macintosh]]		[[Category:Macintosh]]
		+	[[Category:iOS]]

@@ Line 12: / Line 12: @@
   "DTSTR" = "Date";
-The names and values are each enclosed in double quotes, and separated by an equal sign. The line is ended with a semicolon. Extra whitespace outside the quotes is ignored. Also, comments enclosed in /* and */ are ignored (they may span multiple lines).
+The names and values are each enclosed in double quotes (the straight [[ASCII]] variety), and separated by an equal sign. The line is ended with a semicolon. Extra whitespace outside the quotes is ignored. Also, comments enclosed in /* and */ are ignored (they may span multiple lines).
 Strings can then be referenced within [[Objective-C]] code by using:

@@ Line 20: / Line 20: @@
 (using the name of the desired string) in place of a literal string.
-Within OS X apps (inside the .app "file", which is actually a directory and contains multiple items, though the Mac Finder treats it as a single file), you may find .strings files named '''Localizable.strings''' or '''InfoPlist.strings''' in the Resources subdirectory, or in multiple subdirectories for different-language localizations if there are any. These are stored in the [[UTF-16]] character encoding (so if you open them in a viewer/editor not supporting UTF-16, they may appear to have blank spaces in between characters, since ASCII characters end up having two-byte encodings in which one byte is null (00) and the other is equal to the ASCII value). They are [[Endianness|little-endian]], with a [[Byte Order Mark]] (UxFEFF, which shows up as the bytes FF FE) at the beginning. Line breaks are done with linefeed (Ux000A).
+Within OS X apps (inside the .app "file", which is actually a directory and contains multiple items, though the Mac Finder treats it as a single file), you may find .strings files named '''Localizable.strings''' or '''InfoPlist.strings''' in the Resources subdirectory, or in multiple subdirectories for different-language localizations if there are any. These are stored in the [[UTF-16]] character encoding (so if you open them in a viewer/editor not supporting UTF-16, they may appear to have blank spaces in between characters, since ASCII characters end up having two-byte encodings in which one byte is null (00) and the other is equal to the ASCII value). They are [[Endianness|little-endian]], with a [[Byte Order Mark]] (U+FEFF, which shows up as the bytes FF FE) at the beginning. Line breaks are done with linefeed (U+000A).
 Within iOS apps, the structure and filenames are similar, but the format is [[Property List/Binary]].

← Older revision		Revision as of 05:13, 21 January 2013
Line 29:		Line 29:
	* [https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPInternational/Articles/StringsFiles.html Apple's description of .strings files]		* [https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPInternational/Articles/StringsFiles.html Apple's description of .strings files]
	* [http://www.raywenderlich.com/2876/how-to-localize-an-iphone-app-tutorial iPhone app localization tutorial]		* [http://www.raywenderlich.com/2876/how-to-localize-an-iphone-app-tutorial iPhone app localization tutorial]
		+
		+	[[Category:Macintosh]]

@@ Line 7: / Line 7: @@
 A '''strings file''' is used in Mac OS X or iOS apps for localization of text. There can be several versions of the strings file for different languages, and the program code of the app references named strings from that file instead of the literal string values, so the actual text can change based on the user configuration.
-There are several different formats this file can take. They can be encoded as [[Property List]]s, or they can be stored in a "native" strings-file format consisting of name/value pairs as follows:
+There are several different formats this file can take. They can be encoded as [[Property List]]s (with a dictionary as the top-level node, and the name/value pairs of the strings file as its entries), or they can be stored in a "native" strings-file format consisting of name/value pairs as follows:
   "NMSTR" = "Name";
@@ Line 20: / Line 20: @@
 (using the name of the desired string) in place of a literal string.
-Within OS X apps (inside the .app "file", which is actually a directory and contains multiple items, though the Mac Finder treats it as a single file), you may find .strings files named '''Localizable.strings''' or '''InfoPlist.strings''' in the Resources subdirectory, or in multiple subdirectories for different-language localizations if there are any. These are stored in the [[UTF-16]] character encoding (so if you open them in a viewer/editor not supporting UTF-16, they may appear to have blank spaces in between characters, since ASCII characters end up having two-byte encodings in which one byte is null (00) and the other is equal to the ASCII value). They are little-endian, with a [[Byte Order Mark]] (UxFEFF, which shows up as the bytes FF FE) at the beggining. Line breaks are done with linefeed (Ux000A).
+Within OS X apps (inside the .app "file", which is actually a directory and contains multiple items, though the Mac Finder treats it as a single file), you may find .strings files named '''Localizable.strings''' or '''InfoPlist.strings''' in the Resources subdirectory, or in multiple subdirectories for different-language localizations if there are any. These are stored in the [[UTF-16]] character encoding (so if you open them in a viewer/editor not supporting UTF-16, they may appear to have blank spaces in between characters, since ASCII characters end up having two-byte encodings in which one byte is null (00) and the other is equal to the ASCII value). They are [[Endianness|little-endian]], with a [[Byte Order Mark]] (UxFEFF, which shows up as the bytes FF FE) at the beggining. Line breaks are done with linefeed (Ux000A).
 Within iOS apps, the structure and filenames are similar, but the format is [[Property List/Binary]].