Translate feature request


#1

Would it be possible to add a an optional string input to the translate function for comments, then somehow make a translation file with comments using the tool in the introjucer? This is so a localizer can use the translation file without making assumptions.

 [I've just been tripped by right=correct vs right=not-left]


#2

Hmm. Not a bad idea, but don't think I have time to do it right now. Wouldn't it make more sense to use a normal C++ comment than to have an extra argument though?

E.g. you could write

String foo = TRANS("xyz" /* this is my comment */);

As long as the comment is inside the brackets, the parse would be able to find it.

 


#3

Yep. That would make more sense. I've been looking at NSLocalizedString for inspiration.