> - Peter E
>
> On Aug 7, 2014, at 12:00 PM, cocoa-dev-requ...@lists.apple.com wrote:
>> Message: 5
>> Date: Thu, 07 Aug 2014 08:43:04 +0200
>> From: Totte Alm
>> To: "cocoa-dev@lists.apple.com List"
>> Subject: NSNumberFormatter negative and N
On Thu, Aug 7, 2014, at 03:28 PM, Peter Edberg wrote:
> Seems like the bug here is trying to save the file as WindowsLatin1.
I'm not sure how you intended this to be interpreted. If you meant it in
the sense of "the bug involves saving as WindowsLatin1", then I agree.
The saving process should han
> On Aug 7, 2014, at 1:28 PM, Peter Edberg wrote:
>
> This is intentional. The character is ‘−’ U+2212 MINUS SIGN with UTF-8
> representation 0xE2 0x88 0x92. Many locales prefer the proper Unicode minus
> sign for negative numbers, instead of using U+002D HYPHEN-MINUS.
Yup, this is typographi
Aug 7, 2014, at 12:00 PM, cocoa-dev-requ...@lists.apple.com wrote:
> Message: 5
> Date: Thu, 07 Aug 2014 08:43:04 +0200
> From: Totte Alm
> To: "cocoa-dev@lists.apple.com List"
> Subject: NSNumberFormatter negative and NSWindowsLatin1
> Message-ID:
> Content-Type:
Hello,
In 10.9 I (or a client really) just stumbled upon a weirdness regarding
NSNumberFornatter (Swedish default settings), where a negative number is
transformed to a string and that string is later written to a file using
NSString Write..
The - sign (minus) that NSNumberFormatter puts int
