I’d usually go with this:
MSSTR(NSLocalizedString(@“ui.approxTimeFormat”, nil),
MSLocalizedTimeInterval(timeInterval))
In en_US it expands:
ui.approxTimeFormat = “Approx. %@“
In zh_CN:
ui.approxTimeFormat = “大约 %@后“
Note: MSSTR(...) is a macro expands to [NSString stringWithFormat:__VA_ARGS_
I’m fairly sure the answer’s no, but is there any way to get a localized
time-estimate string, given a NSTimeInterval? e.g. “about 10 seconds”, etc for
progress indicators and the like.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> On Nov 28, 2013, at 5:27 AM, Graham Cox wrote:
>> On 28 Nov 2013, at 1:14 am, Shane Stanley wrote:
>>
>> Or write a one-line AppleScript script:
>>
>> do shell script "defaults delete ..."
>>
>> Save it as a code-signed app, send it to them, and tell them to
>> double-click. A lot easier t
On 28 Nov 2013, at 10:05 PM, Bill Cheeseman wrote:
> Did the AppleScript I posted to this thread yesterday not make it to the list?
It did, although I admit I just glossed over it. But from the perspective of
what support staff hand out, I think a hard-coded script is a better option.
That way
Le 28 nov. 2013 à 12:05, Bill Cheeseman a écrit :
>
> On Nov 27, 2013, at 7:14 PM, Shane Stanley wrote:
>
>> On 28 Nov 2013, at 7:53 AM, Graham Cox wrote:
>>
>>> I guess if/when it crops up again we’ll just have to navigate the
>>> unfortunate user through the command line.
>>
>> Or write
On Nov 27, 2013, at 7:14 PM, Shane Stanley wrote:
> On 28 Nov 2013, at 7:53 AM, Graham Cox wrote:
>
>> I guess if/when it crops up again we’ll just have to navigate the
>> unfortunate user through the command line.
>
> Or write a one-line AppleScript script:
>
> do shell script "defaults de
On 28 Nov 2013, at 1:14 am, Shane Stanley wrote:
> Or write a one-line AppleScript script:
>
> do shell script "defaults delete ..."
>
> Save it as a code-signed app, send it to them, and tell them to double-click.
> A lot easier than navigating Library folders for the average user.
Good id
On 27 Nov 2013, at 11:29 pm, Quincey Morris
wrote:
> You make reasonable points, but the fact that your explanation does a lot of
> tap dancing to get there might suggest an overreaction
Hmm, well, short summary: bugs happen.
> In these circumstances, I’d suggest you consider an “alternate”
