Getting localized NSPredicateEditor

2008-10-28 Thread Markus Spoettl
Hello List, is there a way to make NSPredicateEditor play nice with localized versions of an application, meaning that it's rule operators and criteria are translated to the language the rest of the application is using? Right now it appears that NSPredicateEditor uses English operator

Re: Getting localized NSPredicateEditor

2008-10-28 Thread Peter Ammon
On Oct 28, 2008, at 1:12 PM, Markus Spoettl wrote: Hello List, is there a way to make NSPredicateEditor play nice with localized versions of an application, meaning that it's rule operators and criteria are translated to the language the rest of the application is using? Right now it

Re: Getting localized NSPredicateEditor

2008-10-28 Thread Markus Spoettl
Hi Peter, On Oct 28, 2008, at 2:10 PM, Peter Ammon wrote: Apple does not provide any translations of the operator names or criteria. This is because NSPredicateEditor is designed to be localized with sentence granularity, not word by word. Translating each word independently and piecing

Re: Getting localized NSPredicateEditor

2008-10-28 Thread Markus Spoettl
Hi Peter, On Oct 28, 2008, at 3:33 PM, Markus Spoettl wrote: 10/28/08 3:20:54 PM myApp[43721] Error parsing localization! Key: %d %@ Value: %1$d %2$@ Error is: The maximum given order was 2, but nothing has order 1. The localization part looks like this: Never mind the

Re: Getting localized NSPredicateEditor

2008-10-28 Thread Peter Ammon
On Oct 28, 2008, at 3:33 PM, Markus Spoettl wrote: Hi Peter, Let me know if you have any questions, I do! I tried to localize the All/Any/None sentence for the German localization. When I do this I get an exception and the following console log: 10/28/08 3:20:54 PM myApp[43721] Error

Re: Getting localized NSPredicateEditor

2008-10-28 Thread Markus Spoettl
On Oct 28, 2008, at 3:57 PM, Peter Ammon wrote: Here's something that may help - there's a method on NSRuleEditor: - (NSData *)_generateFormattingDictionaryStringsFile. It gives you a strings file (as UTF16 data) appropriate for that control - write the data to a .strings file and then you