"Use Base Localization" only works when you have just opened file to localize
| Originator: | karelia | ||
| Number: | rdar://13248887 | Date Originated: | 19-Feb-2013 04:42 PM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Xcode 4.6 (4H127) |
| Classification: | Other Bug | Reproducible: | Always |
Summary: When you choose "Use Base Localization", it only finds files to localize if you have just chosen the files in Xcode, and then when adding a language, it only creates ".strings" files if you have just chosen the files in Xcode. Steps to Reproduce: 1. In Mountain Lion, Create a new project in Xcode. Cocoa Application, Create Document-Based Application 2. Verify that the project file is selected in the file navigator. DO NOT SELECT THE XIB FILES YET. 3. In the main editor, the target icon should be initially selected. Select the "Project" icon. 4. Click "Use Base Internationalization" checkbox. Expected Results: In the "Choose files and reference language to create Base Localization" sheet, I should see the Document and MainMenu ".xib" files listed there. Actual Results: The sheet contains no files! ---- BUT WAIT, THERE'S MORE. ------ 5. Dismiss the sheet. 6. In the file sheet, click on the icons for the document and the MainMenu xib, so that each nib is showing in the main editor. 7. Now go back to the project icon in the file navigator. 8. Once again, click on "Use Base Internationalization" Expected Results: You shouldn't have had to open those .xib files to see them in the list Actual Results: NOW the files show up in the file list! Huh? ---- BUT WAIT, THERE'S MORE. ------ 9. Dismiss the sheet. 10. From the "+" button in the list of localizations, choose a new language to add, e.g. French. (IMPORTANT: Do not select your xib files in the file navigator first!) Expected Results: In the sheet that comes up, there should be three columns: Resource File, Reference Language, and File Types. The third column should let you choose "Localizable Strings". After finishing, you should be able to disclose the localizations in the file navigator and see that the nib files have .strings files for their newly-added language. Actual results: There is no third column for selecting whether to make a .strings file or a .xib file! And, if you disclose the localizations in the file navigator, you will see that the localizations are xib files -- definitely NOT what we want. ---- BUT WAIT, THERE'S MORE. ------ 11. Dismiss the sheet, if needed. 12. This time, go to the file navigator and select the .xib files so that they load into the main editor view. 13. Go back to the Project icon in the navigator 14. Add another language from the "+" button. Expected Results = Actual Results : There is our third column allowing us to choose "Localizable Strings" Regression: Notes: So apparently, the ability to add files for Base Localization, and the ability to add Strings files to localization, depends on the files having been recently opened in the file navigator. So this appears to be two separate failures! If these instructions are hard to follow, or if you just want to sit back and see the problem, you can check out a movie of these steps! Get it here: https://dl.dropbox.com/u/1284131/radars/BaseLocalizationFailures.mov
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!