Mpf...
Quando Posterous supporterà le diverse timezone sarà sempre troppo tardi.
Explore Posterous
Search posterous
Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
More posterous blogs
Here are posterous posts filed under internationalization...
Introduction to Internationalization (i18n) : From text to bits
One slide out of very nice Introduction to I18N presentation that reminds me of all the basic concepts.
Slide 34 of http://www.inter-locale.com/whitepaper/IUC-Intro-to-I18N-Tutorial.pdf by Addison Phillips
Variable width encodings use different numbers of code units to represent different types of characters within the same encoding
Multibyte Encoding: Any “variable-width” encoding that uses the byte as its code unit.
iconv on unix systems to convert between encodingsUnicode is a character set that supports all of the world’s languages and writing systemsUnicode and ISO 10646 are maintained in sync
* Divide Unicode in equal sized regions of code points.
* 17 planes (0 through 0x10), each with 65,535 characters.
* Plane 0 is called the Basic Multilingual Plane (BMP).
o > 99% of text in the wild lives in the BMP
* Planes 1 through 0x10 are called supplementary planes.Unicode Encodings:
* UTF-32
o Uses 32-bit code units.
o All characters are the same width.
* UTF-16
o Uses 16-bit code units.
o BMP characters use one 16-bit code unit.
o Supplementary characters use two special 16-bit code units: a “surrogate pair”.
* UTF-8
o Uses 8-bit code units (bytes!)
o It’s a multi-byte encoding!
o Characters use between 1 and 4 bytes.
o ASCII is ASCII in UTF-8
Also Interesting:
http://www.yale.edu/pclt/encoding/
Välkommen
欢迎
bienvenue
Willkommen
benvenuto
ようこそ
환영
bienvenido
We've been working hard today fixing issues with international characters on the site. If you see any more issues please don't hesitate to email us at help@posterous.com.
Bug with International Characters Really Fixed
Ok, I admit we did inadequate testing on the last internationalization bugfix. We fixed sending international characters from the operator to the website client, but not the other way around. Hab.la should now fully support any character that you can encode in UTF-8. We have not tested it with UTF-16, because I am unaware of jabber clients that support UTF-16 encoding, please let me know if you need UTF-16 encoding (i.e. if the current release of Hab.la does not work for your browser/language/charset).
I also made some tweaks to the Javascript to make it smarter about the way it reconnects to the server when we are deploying new versions of our software. I.e. it is currently very easy to update the RPC server, without needing the javascript clients to reload their webpages etc.
In other news, I have begun to implement a WIKI for Hab.la’s API documentation, so maybe they’ll be some API docs coming soon :-)
Tutorials!
I'll be the first to admit that writing tutorials is not the most fun task in the world, but I've completed nice hab.la tutorials for iChat and Adium to augment the AppleScript installers. Writing all those tutorials made me think that it would be really cool if A. Tutorials were done on a Wiki and B. Help was internationalized, and by internationalized I mean -- wouldn't it be cool to have tutorials for pirates, Yarr!
I did a little bit of research, and found a nice comparison of the available internationalization options on the Rails Wiki. Of course I can't imagine how you could merge a Wiki and internationalization, so it looks like we'll have to pick one or the other -- or at the very least split the help documentation between a Wiki and more static internationalized documents. I'll see what the rest of the team thinks tomorrow.
Tutorials!
I'll be the first to admit that writing tutorials is not the most fun task in the world, but I've completed nice hab.la tutorials for iChat and Adium to augment the AppleScript installers. Writing all those tutorials made me think that it would be really cool if A. Tutorials were done on a Wiki and B. Help was internationalized, and by internationalized I mean -- wouldn't it be cool to have tutorials for pirates, Yarr!
I did a little bit of research, and found a nice comparison of the available internationalization options on the Rails Wiki. Of course I can't imagine how you could merge a Wiki and internationalization, so it looks like we'll have to pick one or the other -- or at the very least split the help documentation between a Wiki and more static internationalized documents. I'll see what the rest of the team thinks tomorrow.
