FROM : Jim Hamilton
DATE : Tue Apr 19 20:26:31 2005
[oops, forgot to copy to the list]
On Apr 19, 2005, at 1:53 PM, August Trometer wrote:
> I have a situation where I need to create some HTML on the fly and
> save it to a file, then turn around and have WebKit read the file
> using a file:// URL. (Why? NDA until the 29th.)
>
> If I give WebKit the straight string, it handles any UTF-8 characters
> just fine.
>
> However, when I save to a file (using NSString
> writeToFile:atomically), it doesn't save as UTF-8 and when the file is
> read I get all kinds of bogus characters.
Ahem:
> writeToFile:atomically:
>
> - (BOOL)writeToFile:(NSString *)path atomically:(BOOL)flag
> Writes the contents of the receiver to the file specified by path.
> path is written in the default C-string encoding if possible (that is,
> if no information would be lost), in the Unicode encoding otherwise.
I don't know about you, but I kind of want to know exactly what's
getting written before I start. In any case, neither of those choices
is UTF-8.
Try writing directly what's pointed by the pointer returned by -
UTF8String, or putting that into an NSData and using its
writeToFile:atomically: method.
Also:
>
> Can someone point me in the right direction to be able to save the
> HTML string as a UTF-8 encoded file?
1) Do you start the file with a BOM? (Check unicode.org to be sure,
but I think it's 0xEF 0xBB 0xBF.)
2) Does your HTML have an encoding tag? ("charset=utf-8" in a meta
tag)
HTH,
Jim H
--
Jim Hamilton
Senior Software Engineer
Fine Point Technologies, Inc.
139 Centre Street, 6th floor
New York, NY 10013-4408
phone: +1.212.962.7410 ext. 316
fax: +1.212.962.7404
email: <email_removed>
web: http://www.finepoint.com
DATE : Tue Apr 19 20:26:31 2005
[oops, forgot to copy to the list]
On Apr 19, 2005, at 1:53 PM, August Trometer wrote:
> I have a situation where I need to create some HTML on the fly and
> save it to a file, then turn around and have WebKit read the file
> using a file:// URL. (Why? NDA until the 29th.)
>
> If I give WebKit the straight string, it handles any UTF-8 characters
> just fine.
>
> However, when I save to a file (using NSString
> writeToFile:atomically), it doesn't save as UTF-8 and when the file is
> read I get all kinds of bogus characters.
Ahem:
> writeToFile:atomically:
>
> - (BOOL)writeToFile:(NSString *)path atomically:(BOOL)flag
> Writes the contents of the receiver to the file specified by path.
> path is written in the default C-string encoding if possible (that is,
> if no information would be lost), in the Unicode encoding otherwise.
I don't know about you, but I kind of want to know exactly what's
getting written before I start. In any case, neither of those choices
is UTF-8.
Try writing directly what's pointed by the pointer returned by -
UTF8String, or putting that into an NSData and using its
writeToFile:atomically: method.
Also:
>
> Can someone point me in the right direction to be able to save the
> HTML string as a UTF-8 encoded file?
1) Do you start the file with a BOM? (Check unicode.org to be sure,
but I think it's 0xEF 0xBB 0xBF.)
2) Does your HTML have an encoding tag? ("charset=utf-8" in a meta
tag)
HTH,
Jim H
--
Jim Hamilton
Senior Software Engineer
Fine Point Technologies, Inc.
139 Centre Street, 6th floor
New York, NY 10013-4408
phone: +1.212.962.7410 ext. 316
fax: +1.212.962.7404
email: <email_removed>
web: http://www.finepoint.com
| Related mails | Author | Date |
|---|---|---|
| August Trometer | Apr 19, 19:53 | |
| Ondra Cada | Apr 19, 20:23 | |
| Jim Hamilton | Apr 19, 20:26 | |
| Douglas Davidson | Apr 19, 20:26 | |
| Shawn Erickson | Apr 19, 20:30 | |
| Tim Gogolin | Apr 19, 20:31 | |
| Shawn Erickson | Apr 19, 20:35 | |
| Sherm Pendley | Apr 19, 20:39 | |
| John Stiles | Apr 19, 20:44 | |
| August Trometer | Apr 19, 20:57 | |
| Ondra Cada | Apr 19, 21:18 |






Cocoa mail archive

