• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [RESOLVED] Localizable.strings not happening
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RESOLVED] Localizable.strings not happening


  • Subject: Re: [RESOLVED] Localizable.strings not happening
  • From: Kiran B <email@hidden>
  • Date: Sun, 21 Dec 2008 11:22:06 +0530

Another quick way(or On Demand Validation),

In Xcode, open the Strings File you would wish to validate. Then run the following script from Script Menu:
Script Menu->Property Lists->"Parse File as Property List"


This will notify about the missing semicolon. The error would be of the form :
----------------------------------------
<Filename>.strings:
XML parser error:
Unexpected character / at line 1
Old-style plist parser error:
Missing ';' on line <LINE NUMBER>
----------------------------------------


I use this every time I update the Strings file just to be sure of the file integrity. There is another script "Parse Selection as Property List" which will validate only the selection.
Note that these scripts make use of "plutil -lint" internally. So you would get all the error plutil would catch.


- Kiran


On 20-Dec-08, at 1:50 AM, Greg Guerin wrote:

Lance Drake wrote:

"sMW_SoftwareTitle" = "Software";
"sMW_FirmwareTitle"
"sMW_StatusTitle" = "Status";

No clue to this fatal anomaly was represented anywhere I came across.
It would have been great if there was a complaint manifested somewhere.

See this:

http://developer.apple.com/documentation/MacOSX/Conceptual/BPInternational/Articles/StringsFiles.html

At the end is the heading "Debugging Strings Files". It suggests using /usr/bin/plutil with the -lint option to uncover some errors. I suggest trying that command on your defective strings file, and if it correctly detects the error, embodying the command as a step in your build sequence, so it executes every time you do a build.

 -- GG

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: [RESOLVED] Localizable.strings not happening (From: Greg Guerin <email@hidden>)

  • Prev by Date: stdout redirect in xcode and not
  • Next by Date: Adding frameworks question...
  • Previous by thread: Re: [RESOLVED] Localizable.strings not happening
  • Next by thread: [RESOLVED] NSBox over NSImage wipes NSImage on MacOS 10.4
  • Index(es):
    • Date
    • Thread