Thanks for the summary, Steve. I have a better un...
Anonymous · 2006-02-25T00:32:00
Thanks for the summary, Steve. I have a better understanding of character encoding now, although I'm in the same boat: some supplemental materials would be great.
The basic element of Unicode isn't a character, bu...
Anonymous · 2006-02-25T15:54:00
The basic element of Unicode isn't a character, but a code point.
Nor are character sets fundamental to Unicode--Unicode is just one big set of code points, and encodings map those Platonic code points to various character sets.
At least as I understand it...
The basic element of Unicode isn't a character, bu...
Anonymous · 2006-02-25T15:54:00.001000
The basic element of Unicode isn't a character, but a code point.
Nor are character sets fundamental to Unicode--Unicode is just one big set of code points, and encodings map those Platonic code points to various character sets.
At least as I understand it...
I was trying to log what David said as accurately ...
Steve · 2006-02-28T13:01:00
I was trying to log what David said as accurately as I could, rather than correct him on the fly, and given the deadline I'd given myself (to publish before the next session) I had no chance to seek clarification from him - the slides for his talk weren't available at the time.
Technically I believe each Unicode character has a name (such as "PERCENT SIGN") and a code point (such as U+0025) and that a character set maps a (sub)set of Unicode characters to their representations. I had to cover Unicode in Python Web Programming, so owners of that book can check my understanding there.
However, for those wanting to study these things in more detail I can offer two references: Unicode Secrets by Uche Ogbuji is useful for its list of resources, one of which is Unicode for Programmers by Jason Orendorff
Thanks for your article.I work in a latinamerican ...
Anonymous · 2006-03-01T16:54:00
Thanks for your article. I work in a latinamerican country, where unicode provoked me more than one headache and legal problems. Frecuently I receive many ascii files to process and many programs compiled under, -specifically .NET - that read this files, assume unicode so, when I read, for example "España" or "América" I "dangerously" get "Espa?a" or "Am?rica" as output. I mean, the interchange of information between ascii and unicode files is really critical. Do you know which is the solution? How can I avoid to worry if a file is in ascii or unicode format? and that the encoding between ascii and unicode is well done?? Many, many thanks!!
Your thanks, of course, should principally go to D...
Steve · 2006-03-01T18:59:00
Your thanks, of course, should principally go to David Goodger, who took the time to prepare and present the session. We should be grateful to all the PyCon speakers. It takes a lot of work to put a short presentation together.
It seems that the only way to avoid worries about whether a file is in ASCII or Unicode is if everyone used Unicode all the time. There are some strategies that you can use to determine the incoming representation, but they aren't guaranteed to work and so you can always end up making the wrong decision.
Marc André Lemburg and Martin von Löwis are the people whose names I tend to regard as authoritative in this area for the Python world. It's probably worth Googling for those names and the word "unicode" to see what's available in the Python world.
Thanks for the summary, Steve. I have a better un...
Anonymous · 2006-02-25T00:32:00
Thanks for the summary, Steve. I have a better understanding of character encoding now, although I'm in the same boat: some supplemental materials would be great.The basic element of Unicode isn't a character, bu...
Anonymous · 2006-02-25T15:54:00
The basic element of Unicode isn't a character, but a code point.Nor are character sets fundamental to Unicode--Unicode is just one big set of code points,
and encodings map those Platonic code points to various character sets.
At least as I understand it...
The basic element of Unicode isn't a character, bu...
Anonymous · 2006-02-25T15:54:00.001000
The basic element of Unicode isn't a character, but a code point.Nor are character sets fundamental to Unicode--Unicode is just one big set of code points,
and encodings map those Platonic code points to various character sets.
At least as I understand it...
I was trying to log what David said as accurately ...
Steve · 2006-02-28T13:01:00
I was trying to log what David said as accurately as I could, rather than correct him on the fly, and given the deadline I'd given myself (to publish before the next session) I had no chance to seek clarification from him - the slides for his talk weren't available at the time.Technically I believe each Unicode character has a name (such as "PERCENT SIGN") and a code point (such as U+0025) and that a character set maps a (sub)set of Unicode characters to their representations. I had to cover Unicode in Python Web Programming, so owners of that book can check my understanding there.
However, for those wanting to study these things in more detail I can offer two references: Unicode Secrets by Uche Ogbuji is useful for its list of resources, one of which is Unicode for Programmers by Jason Orendorff
Thanks for your article.I work in a latinamerican ...
Anonymous · 2006-03-01T16:54:00
Thanks for your article.I work in a latinamerican country, where unicode provoked me more than one headache and legal problems.
Frecuently I receive many ascii files to process and many programs compiled under, -specifically .NET - that read this files, assume unicode so, when I read, for example "España" or "América" I "dangerously" get "Espa?a" or "Am?rica" as output.
I mean, the interchange of information between ascii and unicode files is really critical. Do you know which is the solution? How can I avoid to worry if a file is in ascii or unicode format?
and that the encoding between ascii and unicode is well done??
Many, many thanks!!
Your thanks, of course, should principally go to D...
Steve · 2006-03-01T18:59:00
Your thanks, of course, should principally go to David Goodger, who took the time to prepare and present the session. We should be grateful to all the PyCon speakers. It takes a lot of work to put a short presentation together.It seems that the only way to avoid worries about whether a file is in ASCII or Unicode is if everyone used Unicode all the time. There are some strategies that you can use to determine the incoming representation, but they aren't guaranteed to work and so you can always end up making the wrong decision.
Marc André Lemburg and Martin von Löwis are the people whose names I tend to regard as authoritative in this area for the Python world. It's probably worth Googling for those names and the word "unicode" to see what's available in the Python world.
Page 1 of 1
Back to post