On Aug 12, 2008, at 2:04 PM, Andy Lee wrote:
This is also good:
http://icu-project.org/userguide/unicodeBasics.html
I found this much clearer and better-written than the first document
you referenced. It defines terms and concepts in an orderly
progression. But I would have found it dr
Count me as another Spolsky defender.
On Aug 12, 2008, at 12:13 PM, Deborah Goldsmith wrote:
On Aug 12, 2008, at 8:41 AM, Kyle Sluder wrote:
http://www.joelonsoftware.com/articles/Unicode.html
That article is missing several concepts which are essential for
understanding Unicode; like many
On Tue, Aug 12, 2008 at 12:13 PM, Deborah Goldsmith <[EMAIL PROTECTED]> wrote:
> That article is missing several concepts which are essential for
> understanding Unicode; like many programmers, Mr. Spolsky thinks of Unicode
> as "wide ASCII", which it is not. The article doesn't cover surrogate pai
On Aug 12, 2008, at 9:13 AM, Deborah Goldsmith wrote:
"The Absolute Minimum Every Software Developer
Absolutely, Positively Must Know About Unicode and Character Sets (No
Excuses!)":
http://www.joelonsoftware.com/articles/Unicode.html
That article is missing several concepts which are essenti
On Aug 12, 2008, at 8:41 AM, Kyle Sluder wrote:
On Mon, Aug 11, 2008 at 9:30 PM, Deborah Goldsmith
<[EMAIL PROTECTED]> wrote:
Anyone who is considering writing code that looks through the
contents of an
NSString (as opposed to just treating the whole string as a unit)
needs to
learn the bas
On Mon, Aug 11, 2008 at 9:30 PM, Deborah Goldsmith <[EMAIL PROTECTED]> wrote:
> Anyone who is considering writing code that looks through the contents of an
> NSString (as opposed to just treating the whole string as a unit) needs to
> learn the basics of processing Unicode.
Joel Spolsky has a gre
This is not a good approach for a number of reasons.
First, Unicode distinguishes between a "code point" (an encoded
character), a "code unit" (one 16-bit unichar), and a "grapheme
cluster" (what the user thinks of as a character). They're all
different. A grapheme cluster may consist of on
I'm a newbie myself but this might help you:
As far as I know,
[ob characterAtIndex:]
(replacing with the character you are after)
..will extract the single character at index .
For example:
NSLog(@"%c",[ob characterAtIndex:i]);
Outputs to the console that character in question.
P
On Aug 7, 2008, at 10:27 PM, SridharRao M wrote:
Hi,I want to retrieve characters from NSString Can any one guide me
how to
do it.
What do you mean by that? If you want to translate an NSString into a
C char array, then use -UTF8String. If you want to get a range of 2-
byte characters f
Not to reply to myself, but -- erm -- that second one should be -
[NSString getCharacters:range:] -- with a second colon (this one after
"range"). Also, sorry for top-posting, but I had to since I neglected
to bottom post in my original reply.
Cheers,
Andrew
On Aug 7, 2008, at 9:53
Hi!
Would -[NSString getCharacters:] or -[NSString getCharacters:range]
(both of which return a unichar array), or better yet -[NSString
getCString:maxLength:encoding:] work for your purposes?
Even better still, perhaps one of
- [NSString cStringUsingEncoding:]
- [N
Hi,I want to retrieve characters from NSString Can any one guide me how to
do it.
Ex:
NSString *ob=@"TEST Object";
Now how to retrieve the "Test Object " value into my Char Array.
Regards,
Sri.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Pl
12 matches
Mail list logo
