A better approach when using NSLocalizedString and its variants is to
always use a highly non-user-friendly string for the key that matches the
definitive meaning behind the particular string.
One benefit is that when you see that string in your UI, you know you
don't have a translated string for
On 10 Oct 2012, at 11:45, Ken Thomases wrote:
> On Oct 10, 2012, at 4:25 AM, Luc Van Bogaert wrote:
>
>> I'm in the process of localising my application, and I'm having a problem
>> getting some of the string resources in my code localised. In several places
>> in my code, I'm using this kind
On Oct 10, 2012, at 4:25 AM, Luc Van Bogaert wrote:
> I'm in the process of localising my application, and I'm having a problem
> getting some of the string resources in my code localised. In several places
> in my code, I'm using this kind of structure to implement "dynamic" menu
> items:
>
>
Hi,
I'm in the process of localising my application, and I'm having a problem
getting some of the string resources in my code localised. In several places in
my code, I'm using this kind of structure to implement "dynamic" menu items:
if (action == @selector(toggleInspectorPanel:)) {
