All supported languages now have accepted or at least proposed translations. We can remove the old string now.

@kambala-decapitator, the bug when using Turkish language was a really great example of bad design.

@kambala-decapitator, the bug when using Turkish language was a really great example of bad design.

I think we already had this discussion about checking user-visible strings vs some kind of internal identifier (numeric or string) :)

I think we already had this discussion about checking user-visible strings vs some kind of internal identifier (numeric or string) :)

Yes, we had this kind of problem twice in the past years. Seems UIAlertAction is not directly supporting tag or something else. So I would need to create a new class which has an additional member tag and in the handler check for this instead of the action's string.

it's almost trivial to modify handler to accept internal identifier, for example:

UIAlertAction* action1 = [UIAlertAction ... handler:^{ [self handler:Action1EnumCase] }];
UIAlertAction* action2 = [UIAlertAction ... handler:^{ [self handler:Action2EnumCase] }];

you could also use objc runtime magic to attach arbitrary data, see objc_setAssociatedObject().

it's almost trivial to modify handler to accept internal identifier, for example:

Hmm, often the action sheet is built in a loop from all defined action strings. In such case I would need to create an array or dictionary for each action to also hold the enum. Nothing I had on my agenda.

yes, array of pairs <key, localization> sounds good. But you'd rather ask yourself: do you really have/need such a generic handler? Maybe easier to write respective code in each separate UIAlertAction handler?

So this would require a bunch of the following actions which covers all needed actions:

UIAlertAction *action1 = [UIAlertAction ... handler:^{ [self do_this] }];
UIAlertAction *action2 = [UIAlertAction ... handler:^{ [self do_that] }];

In this case I would need to move the logic of what I am finally showing in the action sheet (currently a simple array of action strings which is majorly defined in AppDelegate) to the place where I am building the sheet. And ideally replacing the string in AppDelegate with enums. Something like this:

AppDelegate:

menu.sheetActions = @[
    action_play,
    action_queue,
];

DetailViewController:

UIAlertAction *action1 = [UIAlertAction ... handler:^{ [self play] }];
UIAlertAction *action2 = [UIAlertAction ... handler:^{ [self queue] }];

for (actionID in sheetActions) |
    switch (actionID) {
        case action_play:
            [alertCtrl addAction: action1];
            break;
        case action_queue:
            [alertCtrl addAction: action2];
            break;
       default:
           break;
    }
}

Let me create an issue to the backlog. Should anyway not be done here in this PR.