The past two weeks, I’ve had occasion to visit two different hospitals in Shanghai. Both were large, public hospitals that served a huge volume of patients every day. I came away from both feeling that Chinese train stations and Chinese hospitals are very similar.
– Both serve huge numbers of people
– Both contain a wide cross-section of society
– Both involve a lot of helpless waiting and nerve-wracking purchases
– Both offer VIP options which offer English-language services and a quieter, more private atmosphere
– Both leave you with a sense of wonder and hopelessness at the magnitude of the problems heaped on a government which has to provide for 1.3 billion people.
(I can also totally understand why many of the doctors and nurses had attitudes scarcely better than train station ticket vendors.)
I haven’t been blogging much lately because I’ve been looking for a new web host in my spare time. I’ve been with DreamHost for years, but recently their service has become unforgivably bad.
My main complaints are:
- My site was hacked while at DreamHost once. (One time is forgivable)
My site was later hacked again, which was probably due to outdated web app installations (and not the previous hack). But DreamHost proved amazingly unhelpful in shutting out the hacker. I thought I had shut him out once, but I was wrong. The best solution in this case, then, is to back everything up, make sure it’s all clean, then wipe the original installations and start anew. But if I’m going to do all that, I might as well move to a new host that offers better service and better security.
Last weekend my site was down for three days, and DreamHost support never replied to any of my tech requests. I eventually got the attention of a tech support person via live chat, and that person let me know that the security team had actually just moved my site to a different location on the server. Moving it back was trivial. They did it because DreamHost’s WordPress automatic upgrade script creates a backup of the old install (good), but it has a bug which places that directory in a predictable, public location, leaving previous versions’ security exploits online and vulnerable to attack (bad). I was a victim of this bug when I upgraded my WordPress installs, so DreamHost pro-actively (for once) took security measures by moving my entire site’s public directory. They just never told me, and refused to answer my questions. Amazing.
I understand what’s going on here. Basically, I’m the victim of the 80/20 rule. I’m one of those demanding customers who runs multiple sites, and has special needs. It makes a lot more sense for the business to focus on the “easy” customers who have one website that consists entirely of a WordPress install. (Never mind that I’ve brought in lots of referrals over the years, which means more business.)
Anyway, I’ll soon be moving on to a host that still cares more about customer service, and that will be happy to meet my needs. I think I’ve found a good one, but if you have any suggestions, I’d be happy to hear them.
(Incidentally, the first one I tried was Media Temple. The server they randomly assigned me was blocked in China, and when I asked to be switched to a server not blocked in China, the support staff promptly directed me to the refund page. Unbelievable.)
2016 Update: I later switched to WebFaction, and have been very satisfied for years. I recommend it!
John: The long wait for the iPhone app has caused much distress amongst all the Pleco fans out there. Any comments on the development process of your first Pleco iPhone app?
Michael: Well, much of the delay stems from the fact that we really only started working on the iPhone version in earnest in January ’09 – before that we were mainly working on finishing / debugging Pleco 2.0 on Windows Mobile and Palm OS. We laid out the feature map for that back in early 2006, when the iPhone was nothing but a glimmer in Steve Jobs’ eye, so by the time Apple released the first iPhone SDK in Spring ’08 we were already well past the point where we could seriously scale back 2.0 in order to get started on the iPhone version sooner.
But as far as how the actual development has gone, the biggest time drain has been working around the things that iPhone OS doesn’t do very well. We’ve gone through the same process on Palm/WM too – we start off implementing everything in the manufacturer-recommended way only to find that there are certain areas of the OS that are too buggy / slow / inflexible and need to be replaced by our own, custom-designed alternatives.
On iPhone the two big problems were file management and text rendering. There’s no built-in mechanism on iPhone for users to load their own data files onto their devices; all they can do is install and uninstall software. So we had to add both our own web browser (for downloading data files from the web) and our own web server (for uploading data file from a computer) in order to allow people to install their own documents / flashcard lists / etc. We also had to implement a very elaborate system for downloading and installing add-on dictionaries and other data
files; for a number of reasons it wasn’t feasible to bundle all of those into the main software package, and again there was no way for users to install those directly from a desktop as they can on other mobile platforms.
And the iPhone’s text rendering system is actually quite slow and inflexible, which is rather disappointing coming from a company with as long and rich a history in the world of computer typography as Apple. The only official mechanism for drawing rich text (multiple fonts, bold, italic, etc) is to render it as a web page, which took way too long and used way too much memory to be practical for us; there also seem to be some bugs in the way Apple’s WebKit page rendering engine handles pages with a mix of Chinese and non-Chinese text. And even simple, non-rich-text input fields and the like are a big performance hog – it took the handwriting recognizer panel about 8x as long to insert a new character into Apple’s text input box as it did to actually recognize a character. So we basically ended up having to write our own versions of three different iPhone user interface controls in order to get the text rendering to work the way we wanted it too.
So a quick-and-dirty port of Pleco on iPhone could probably have been ready last spring, but getting everything working really smoothly took a lot longer.
I just recently had the pleasure of trying out the beta version of the new Pleco iPhone app. In case you’re not aware, Pleco is the software company behind what is regarded as the best electronic learner’s Chinese dictionary for any mobile device (and possibly the desktop as well). Given the dearth of really good Chinese dictionaries for the iPhone, Chinese learners have been eagerly awaiting the release of this iPhone app for quite some time. The wait has not been in vain; Pleco for iPhone is an outstanding app.
The Video Demo
Michael Love, Pleco founder, has made a two-part video of the new Pleco iPhone app:
For those of you in China, visit Pleco’s mirror site for the videos.
An All-New UI
I’ve never owned a device running Windows Mobile or Palm OS, so I’ve never been able to own Pleco before, but I’m familiar enough with previous versions to make basic comparisons.
The Pleco user interface received a much-needed makeover for the iPhone. While older versions of Pleco squeezed a plethora of buttons and options onto the screen (you have your stylus, after all), this iPhone Pleco had to find ways to increase buttons to tappable sizes and limit button clutter by hiding options on screens where you don’t need them all. Compare (Windows Mobile on the left, iPhone on the right):
> She decided to slum it for a couple of months.
The Chinese sentence, translated back into English, would be:
> She decided to stay in a slum for a couple of months.
I think the translator missed something in this particular case, and the content of the sentences (as well as the order) strongly suggests that the Chinese is a (not so great) translation of the English.
So how nciku is getting its sample sentences for Chinese words? The OED is the champion of the dictionary quotation for the English language, containing tons of examples of its words’ usage “in the wild.” Dictionary sample sentences are best when taken from other sources, but those sentences should at the very least be composed in the language the dictionary serves. It seems this is not what’s happening with nciku, but maybe Collins (one of nciku’s data sources) is to blame.
I just learned recently that in mainland China there’s a whole business centered on getting pregnant women into Hong Kong to give birth so that the babies get extra Hong Kong citizenship privileges. This trend has been dubbed “maternity tourism.” Surreal.
Of course, there’s also a backlash. But anyway, the reasons to do it:
> Giving birth in Hong Kong not only guarantees them world-class health care but in many cases secures citizenship in the city of 7 million for children who would otherwise be entitled only to a Chinese passport.
> Hong Kong citizenship entitles the children to free education, health care and other benefits throughout their life, the equivalent of a lottery win for children from poor families in southern China.
I understand that Hong Kong citizenship means a much easier time getting visas to other parts of the world. What wouldn’t a parent do for her baby’s future, huh?
I’m a bit of a sucker for Venn diagrams. When I was recently asked by a student about the Chinese modal verbs 会, 能, and 可以 (all of which can be translated into English as “can”), I recalled a nice Venn diagram on the topic and dug it up.
What creates the most confusion with these three modal verbs is not that they can all be translated into “can” in English. The problem is that they are usually explained over-simplistically something like this:
> 会: know how to
> 能: be able to
> 可以: have permission to
This is not a bad start, but this sort of definition is eventually revealed as insufficient to the learner because in usage, the three modal verbs actually overlap. Enter the Venn diagram. The image below is a reconstruction of the one on page 95 of Tian Shou-he’s A Guide to Proper Usage of Spoken Chinese:
> A = ability in the sense of “know how to” (“会” is more common than “能“)
> B = permission/request (use “能” or “可以“)
> C = possibility (use “能” or “可以“)
> D = permission not granted (use “不可以“)
> E = impossibility (use “不能“)
Yeah, grammar needs more Venn diagrams.
Update: I’ve been informed that this diagram is actually a Euler Diagram. Oops. I stand corrected. I should have read up on the requirements for Venn Diagrams first! (Hey, some of those extensions are pretty cool!)
Chinese Telegraph Code
[Source: Wikimedia Commons]
Oh, and by the way, in this instance, Google Wave wins, 65% to 35%, making it part of an exclusive club of things harder to understand than Google Wave, which also includes “women, Scientology, the United States Tax code, Chinese telegraph code, Microsoft Visio 2004, and Obama’s Nobel Peace Prize.”
Slow Chinese, as far as I know, is the first site to do this (and just this) for Chinese. I know that the same “slow” concept has already existed for some time for learners of German (Slow German), and that it is quite popular among that learner community. The idea, of course, is that if learners are exposed to enough slowed-down input, they will not only get better at recognizing the words they know, but will also be able to more easily pick out the words they don’t know, and the gains will gradually transfer to normal-speed input.
The linguistic question, of course, is: does this work? Is it a good idea?
First I’ll quote friend and fellow linguist JP Villanueva on what he once said about slow input:
> Listen to me: slow input does NOT help you learn language. No! NO NO NO. At best, slow input helps you learn SLOW LANGUAGE. […] Whenever you get mad at someone for “talking too fast,” you need to remind yourself that you don’t speak that language, and no amount of SLOW is going to help you understand.
> Counter-intuitive? Remember when you learned to ride a bike, and you found that it was easier to balance when you had a little speed? Remember when you first learned to drive, and you realized you had more control with a little speed?
> Same with language. Slow speech doesn’t help your memory. You don’t need every word in a sentence in sequence in order to understand what someone is saying.
> Besides, that’s not how your brain listens to your own native language, anyway. Your brain listens for semantic landmarks and then fills in the information in between. You need to learn to do that in your second language. Slow speech levels semantic landmarks, and over-emphasizes the non-content words that hold sentences together.
When it comes to Slow Chinese, there are actually two relevant questions:
1. Is slow input valuable?
2. Is slow input for news (or other media intended for native speakers) valuable?
In answer to question #1, I’d say yes. JP knows what he’s talking about, but earlier in the same post he also made a few caveats where confidence is concerned, and with good reason. There is a period when a beginner has a really tough time distinguishing the sounds of the target language. Yes, the purists are right when they say that continued, persistent exposure can overcome this obstacle, but most learners are not so hardcore. They’re emotional and easily discouraged. They want some help beyond “don’t give up,” and slowed-down input can provide that much-wanted crutch. It is a crutch, however, so if used, it should be withdrawn as soon as possible. It is most useful for learning the phonetics of the language as a beginner, in individual words and short phrases.
In answer to #2, I’d say no. If a learner is ready to take on media intended for native speakers, he should already be comfortable with the language at natural speed. If he has the vocabulary to take on the media but can’t handle the speed, it is likely because communication as a learning goal has been neglected. One can’t carry on normal conversation without comprehension of speech at a normal rate (unless one limits one’s conversation partners to slow-talkers only). So it seems to me that one would be tackling slow-speed media instead of tackling normal-speed listening comprehension and communication, which under most circumstances is a big mistake.
So my conclusion is that the learner’s time would best be spent working on simpler normal-speed input to improve listening comprehension (for Chinese, most Elementary and Intermediate ChinesePod dialogues are good for this; users can listen to the dialogue-only audio, all of which also have transcripts), and then later tackling normal-speed media.
Still, enthusiasm for learning is a valuable thing, so if Slow Chinese is what you’ve always wanted, I say go for it. (Plus, it’s free!) Just don’t forget that it’s not likely to help you out with conversational fluency, if that’s your goal.
Intermediate students of Chinese will be familiar with the following pattern:
> V + 不起 = can’t afford to V
> V + 得起 = can afford to V
This pattern is most commonly about money, the typical example being 买不起 (can’t afford to buy).
The pattern is fairly productive, so you’ll see it for lots of different verbs (and not always about money), but recently I heard a new one. A friend was saying that she was going to eat at an expensive restaurant, but someone else was getting the bill. She said she ordinarily wouldn’t be able to afford even just her own meal at that restaurant (in China, each person getting her own check is a “system” called AA制), so in this case, she used: AA不起.
Heard any interesting usages lately?
I was delighted to discover churros in Beijing, and with ice cream! (Sure, why not?) But the second English name threw me for a loop: “Kyrgyzstan Things Fruit.”
I don’t know why “churros” wasn’t enough, but apparently this is another casualty of horrible character-by-character machine translation. So we have a case of:
> Foreign word → Chinese transliteration → horrible machine translation to English
> churros → 吉事果 → “Kyrgyzstan Things Fruit”
Why go all the way to machine translation when you started with a foreign word in the first place? Did someone think that the machine translation of a transliteration might help out English speakers? Why is Kyrgyzstan the default translation for 吉?? There are no answers here… moving on.
I thought this was a rather clever bit of signage:
In context, and especially next to its “opposite” icon, there’s absolutely no question what the above icon stands for. Out of context, though, it can be a bit puzzling. I showed this to a few Chinese friends (out of context, of course), and they didn’t get it on their own.
(Hint: No, it has nothing to do with any characters in WALL-E.)
During our recent trip to Beijing, conversation naturally turned to comparisons of Shanghai and Beijing. I don’t want to rehash that tired topic (again) here, but there were three particular anecdotes told by Chinese friends which I found amusing. All involved interactions with the locals in which the storytellers’ values clashed with the locals’.
I’ve recreated them below, in spirit, at least, and translated them to English, but I’m not revealing the cities. See if you can identify the city from the story.
> I wanted to take the bus to the nearest supermarket, so I asked a middle-aged person on the street. The conversation went something like this:
> Me: Excuse me, which bus can I take to the supermarket?
> Man: Bus? What do you want to take a bus for? It’s not that far, and you’re young! Just walk. The weather is great. Go straight up that way 5 blocks, then turn left.
> Me: Thanks, but I’d like to take a bus, so…
> Man: I’m telling you, it’s a great walk! You don’t need a bus! Just walk up that way 5 blocks…
> I wanted to buy a bottle of water in a small store.
> Me: I’ll just take this bottle of water. All I have is a 50.
> Shopkeeper: I can’t change a 50.
> Me: Well, I don’t have change, so…
> Shopkeeper: I told you, I can’t change a 50. Come back when you have change.
> I needed to buy a lighter, so I sought out a nearby convenience store.
> Me: I’d like to buy a lighter, please.
> Cashier: A lighter? You don’t want to buy that here.
> Me: What do you mean?
> Cashier: Lighters are way cheaper at the shop down the street. You save 2 RMB!
> Me: Thanks, but I’d like to just buy one here, so….
> Cashier: I’m telling you, they’re cheaper down the street! You don’t want to throw money away, do you??
Can you identify the cities?
Light posting lately… I just got back from a weekend in Beijing. No sightseeing, no business… just hanging out, taking it easy, and seeing a few friends. Got together with Pepe, Brendan, Joel, Syz, Dave Lancashire, Roddy, and David Moser. And also happened to bump into Rob of Black and White Cat.
My wife and I spent most of our time on Bei Luogu Xiang (北锣鼓巷) or Nan Luogu Xiang (南锣鼓巷). We stayed in a nice little 四合院 hotel in the area called 吉庆堂. Thanks to Brendan, we ended up at a bar called Amilal both nights, which was a pleasant 20-minute walk from our hotel.
We had a good time, and my Shanghainese wife is liking Beijing more every time we go.
You may have heard of Sa Dingding before. Shanghaiist wrote about her a long time ago, and fans of “world music” will have known about her for quite some time. As I understand it, she’s only recently been catching on in China in a big way, which is how I was introduced to her music by a Chinese friend.
From her Last.fm page:
> Sa Dingding is a singer and musician born in Inner Mongolia. She sings in Sanskrit, Tibetan, Lagu, and Mandarin, and also in a self-created language. She plays several instruments, including the zheng, the Chinese drum, Chinese gong, and horse-head fiddle. Inspirations include Buddhism and Dyana Yoga.
You can see why Sa Dingding is an artist that might appeal to linguists! Her unique style is a great example of Chinese creativity, as well.
Her most popular song is 《万物生》 (Alive in English). Here it is in Mandarin [Youku video]:
And here is 《万物生》 in Sanskrit:
If you’re in China, all of Sa Dingding’s music is available for free online from Google.cn music: 萨顶顶 (if only Google would properly ID3tag it!).
You’ll also note that most sources write Sa Dingding’s name as “Sa Ding Ding.” I find this interesting. You don’t write “Deng Xiao Ping” or “Zhang Zi Yi.” The surname is capitalized, and the given name is written as one word, also capitalized. Do people feel that a given name with a reduplicated character must be written so that each syllable is also exactly duplicated?
You can see the same tendency for Fan Bingbing (“Bing Bing”) and Li Bingbing (“Bing Bing”) as well, but the Wikipedia pages for those two actually follow the proper pinyin name-writing convention [see section 2.3]. (Perhaps the “Sa Ding Ding” page will be wiki-harmonized soon? [Update: It was changed within 24 hours! Wow!])
Her own website uses “Sa DingDing” in the HTML title, but “Sa Dingding” on the site pages themselves.
My sister Amy forwarded this thought-provoking article to me: Raising Katie: What adopting a white girl taught a black family about race in the Obama era.
In case it’s not immediately obvious, here’s the focal point of the piece:
> So-called transracial adoptions have surged since 1994, when the Multiethnic Placement Act reversed decades of outright racial matching by banning discrimination against adoptive families on the basis of race. But the growth has been all one-sided. The number of white families adopting outside their race is growing and is now in the thousands, while cases like Katie’s—of a black family adopting a nonblack child—remain frozen at near zero.
> Decades after the racial integration of offices, buses and water fountains, persistent double standards mean that African-American parents are still largely viewed with unease as caretakers of any children other than their own—or those they are paid to look after. As Yale historian Matthew Frye Jacobson has asked: “Why is it that in the United States, a white woman can have black children but a black woman cannot have white children?”
This article made me think back to the time I saw a big group of foreigners at the Shanghai Pudong airport, each couple carrying a precious newly adopted Chinese baby, getting ready to fly back home. I didn’t think anything of it at the time, but now I do realize that all of them were white.
So this does make me wonder… Would a black couple have trouble adopting a Chinese baby in China?
My recent post on the Wikimedia Commons Stroke Order Project prompted Mark of Toshuo.com to decry the relative dearth of traditional characters being added to the project. To this, David on Formosa reminded Mark that there are also a large number of characters shared by the traditional and simplified character sets.
At this point I’ll interject a visual aid (gotta love them Venn diagrams!):
All this got me thinking about the following question: If “s” represents the characters in the simplified set not shared with the traditional set, while “t” represents the characters in the traditional set not shared with the simplified set, and “u” represents the characters shared by the two sets, then what are the number of characters belonging to groups s, t, and u, respectively?
It seems like a simple enough question, but it’s actually quite tricky for a number of reasons.
First, the total number of Chinese characters in existence varies according to source, and largely depends on how many non-standard variants you want to include in your total set. You can be reasonably certain the total number is less than 50,000, but that’s still a pretty ridiculously large number, when most Chinese people regularly use less than 5000. For basic purposes of comparison, it makes sense to limit your set to a certain number of commonly used characters, but which set? One from the PRC? From Taiwan? From Hong Kong? From Unicode?
Second, you might be tempted to think that s = t, because simplified characters were “simplified from” traditional characters. This isn’t true, however, because in many cases multiple traditional forms were conflated into one simplified form. To give a very common example, traditional characters 干, 幹, and 乾 are all written 干 in simplified. So adding these three characters adds 1 to u, 2 to t, and 0 to s. There are lots of similar cases, so clearly t is going to be significantly larger than s. But by how many characters?
I’d be very interested to see a concrete answer to this question, regardless of the character limit used. I also wonder how the proportions of s, t, and u vary as the character limit is increased, and more and more low-frequency characters are included.
If you’ve got an answer, I’d love to hear from you!
This is a screenshot from the Google Pinyin installer:
If you’re learning Mandarin for real, sooner or later you’re going to need to experience the rich variety in pronunciation that Greater China has to offer. This simple “fuzzy pinyin” options screen gives you an idea of what’s out there. (Speakers that can’t differentiate between z/zh, r/l, f/h, etc. typically can’t properly type the pinyin for the words that contain those sounds in standard Mandarin, so fuzzy pinyin input saves them a lot of frustration.)
If you’ve checked out many online Chinese dictionaries or websites on learning Chinese, you’ve seen a variety of ways to present characters’ proper stroke order. Animated GIFs are a favorite, but they often fall flat in one important respect: they display each stroke in a single frame, often leaving the direction of the stroke somewhat unclear.
This is where the Wikimedia Commons Stroke Order Project impresses me: not only are the animated GIFs large and attractive, but they fluidly demonstrate the direction of each stroke. A nice example:
More info from the site:
> Hello, and welcome to the Commons Stroke Order Project. This project aims to create a complete set of high quality and free illustrations to clearly show the stroke order of East Asian characters (hanzi, kanji, kana, hantu, and hanja). The project was started as there was none like it in terms of quality and it seems that it is the only one working on all three schools of Han character stroke order; simplified and traditional Chinese, and Japanese.
> You are free to use the graphics we’ve made and welcomed to join us and contribute to our progress. It’s easy, you just have to follow the simple steps stated in our graphics guidelines.
At 378 total characters, the project is still far from a complete set, but it’s off to a nice start!
I do, wonder, though, what kind of stroke order information is freely available out there that could speed the process along. I’ve seen enough separate sets of animated characters to make me suspect many have been automatically generated. (Anyone have info on this?) I’m also curious how the project is going to deal with the annoying issue of variable stroke orders.
Note that there is also an Ancient Chinese Characters sister project.
We live in a world of fascinating, interactive web services, but unfortunately, those of us in China are cut off from some of the leading websites. Most conspicuous among these are YouTube, Twitter, and Facebook. None of these websites are currently accessible in China, cut off by the Great Firewall (GFW) of China. Twitter and Facebook, most notably, have APIs, which enable other software, web services, and mobile phone apps to connect to and interact with them. But since all of these uses of the API make direct calls to Twitter or Facebook’s servers, none of these work in China either.
Working with Reign Design recently on OpenLanguage, I happened to browse Reign Design’s blog and came across this entry: Posting to Twitter via SMS in China. This interested me because I used to enjoy the convenience of posting to Twitter via SMS, and it’s a way to circumvent the GFW. I stopped because Twitter quit offering local numbers, and international SMSes are a bit expensive just for a tweet.
Anyway, I read the article, and the PHP script looked simple enough, so I headed over to Fanfou, where I already had a seldom-used account. I was surprised to discover, though, that Fanfou is gone. Nothing but a smoking crater where there used to be a lively community. Considering some recent events in China and the immediate, individual-empowering nature of microblogging, it’s not hard to imagine what happened.
With that option closed to me, I decided to check out the other big Chinese microblogging service I was familiar with, Zuosa (做啥). I really liked Zuosa, where I found a lot of advanced features that even Twitter has held back on. Then I went into settings, where I saw the familiar Twitter “t” next to the 同步到微博客 (“Sync to microblogs”) section.
When I clicked on that section, and then on the Twitter “t,” I got this message:
The message says:
> 抱歉，该服务不可用；你可以通过 zuosa->buboo.tw->twitter 实现同步！
> We’re sorry, this service is not available. You can go through zuosa -> buboo.tw -> twitter to accomplish the sync!
So I set up an account on Buboo.tw (ah, traditional characters!), easily synced that with Twitter, then synced my Zuosa account with Buboo. And hey… it works (1, 2, 3)! A tweet on Zuosa appears on Twitter in seconds. And since I synced my Twitter account to Facebook long ago, Facebook is actually at the end of the tweetchain: Zuosa -> Buboo.tw -> Twitter -> Facebook.
I haven’t tested SMS tweeting yet. One of the disadvantages of this method is that you can’t not post “downstream.” So for now, I can’t post only to Zuosa without posting to the other three, or post to Buboo without posting to Twitter and Facebook, unless I turn off the sync.
Anyway, I thought this was pretty cool… all made possible through international open APIs.
I got the Google Pinyin input working for my HTC Hero Android phone. It turned out to be quite simple. The only two things holding me back were (1) a bad install of Google Pinyin, and (2) lack of proper documentation for switching input methods.
When I first got the phone, it already had Google Pinyin installed, but apparently it was an old version that didn’t work properly. I had to uninstall it and reinstall it. To uninstall, go to: Settings > Applications > Manage Applications, and uninstall it from there. The applications may take a while to all load, but Google Pinyin, if installed, should be at the very bottom, listed by its Chinese name, 谷歌拼音输入法. Select it to uninstall it.
After you’ve got the latest version of Google Pinyin from the Android market installed, go to Settings > Locale & text, and make sure that you have Google Pinyin activated. (I turned off Touch Input Chinese because it didn’t seem to work.)
From the menu above, you can also turn on predictive input (联想输入, literally, “associative input”) and sync (同步) your custom words with your Google account. (For some reason this is not automatically synced like the rest of your Google account services are.)
One you’ve got Google Pinyin installed and turned on, you’re ready to type something. For my demo, I went into my SMS messages and opened up one of the recent ones from China Merchant Bank. To switch input modes, you tap and hold the textbox. A menu will pop up, and you choose “Select input method.” Then choose “谷歌拼音输入法.”
Now you’ve got the Google Pinyin soft keyboard. Start typing, and characters will appear. As you can see from my example below, it’s not perfect, but it’s pretty good most of the time. You also have an extra keyboard of symbols in addition to punctuation, which is nice.
I have to say, it’s a bit annoying to have to go through a three-step process every time to change the input method. I could do it with one keypress on the iPhone, but that’s only if I have only one alternate input method installed. As Brendan has pointed out, it could be quite a few extra keypresses depending on how many input methods you have installed. For the time being, on the Hero, it’s always three keypresses.
Anyway, hopefully this helps a few other people figure out how to get Google Pinyin working on an HTC Hero.