Zhou Youguang on NPR

Louisa Lim had a story on National Public Radio yesterday about Zhou Youguang (周有光 / Zhōu Yǒuguāng), who’s often referred to as the father of Pinyin.

Most stories in the mass media about him focus on just two things, which might be summarized as “pinyin” and “wow, he’s really old.” This story, however, draws welcome notice to some some other things about him, as the title reveals: At 105, Chinese Linguist Now A Government Critic. (There’s a link to the audio version near the top of the page. Zhou can be heard in the background speaking Mandarin — though his English is excellent.)

The article also provides a link to his blog: Bǎisuì xuérén Zhōu Yǒuguāng de bókè (百岁学人周有光的博客).

Further reading:

Hat tip to John Rohsenow.

photo of Zhou Youguang signing a book for me

Now on Pinyin.info: Weishenme Zhongwen zheme TM nan?

Earlier this year a Mandarin translation of David Moser’s classic essay Why Chinese Is So Damn Hard appeared on the Web. And then it disappeared. With the permission of both the translator and the original author, I’m placing this work back online.

It’s available here in two versions:

Enjoy!

Maybe I’ll make a Pinyin version too one of these years.

Google Translate’s Pinyin converter: now with apostrophes

Google has taken another major step toward making Google Translate‘s Pinyin converter decent. Finally, apostrophes.

Not long ago “阿爾巴尼亞然而仁愛蓮藕普洱茶” would have yielded “Āěrbāníyǎ ránér rénài liánǒu pǔěr chá.” But now Google produces the correct “Ā’ěrbāníyǎ rán’ér rén’ài lián’ǒu pǔ’ěr chá.” (Well, one could debate whether that last one should be pǔ’ěr chá, pǔ’ěrchá, Pǔ’ěr chá, Pǔ’ěr Chá, or Pǔ’ěrchá. But the apostrophe is undoubtedly correct regardless.)

Also, the -men suffix is now solid with words (e.g., 朋友們 –> péngyoumen and 孩子們 –> háizimen). This is a small thing but nonetheless welcome.

The most significant remaining fundamental problem is the capitalization and parsing of proper nouns.

And numbers are still wrong, with everything being written separately. For example, “七千九百四十三萬五千六百五十八” should be rendered as “qīqiān jiǔbǎi sìshísān wàn wǔqiān liùbǎi wǔshíbā.” But Google is still giving this as “qī qiān jiǔ bǎi sì shí sān wàn wǔ qiān liù bǎi wǔ shí bā.”

On the other hand, Google is starting to deal with “le”, with it being appended to verbs. This is a relatively tricky thing to get right, so I’m not surprised Google doesn’t have the details down yet.

So there’s still a lot of work to be done. But at least progress is being made in areas of fundamental importance. I’m heartened by the progress.

Related posts:

The current state:
screen shot of what Google Translate's Pinyin converter produces as of late September 2011

Google Web fonts and Hanyu Pinyin

Back in the last century, getting Web browsers to correctly display Pinyin was such a troublesome task that I remember once even employing GIFs of first- and third-tone letters to get those to look right. So there were a whole lotta IMG tags in my text. Sure, I put the necessary info in ALT tags (e.g., “alt=’a3′”), just in case. But, still, I shudder to recall having to resort to that particular hack.

Things are better now, though still far from ideal. Something that promises to considerably improve the situation of website viewers not all having the same font you may wish to use is CSS3’s @font-face, which allows those creating Web pages to employ fonts that are provided online. Google is helping with this through its Google Web Fonts. (Current count: 252 font families.)

But is anything in Google’s collection capable of dealing with Hanyu Pinyin? Armed with a handy-dandy Pinyin pangram, I had a look at what Google has made available.

Not surprisingly, most of the 29 font families marked as offering the “Latin Extended” character set failed to handle the entire Hanyu Pinyin set. The ??? group is the most likely to be unsupported at present, with third-tone vowels also frequently missing.

Here are the Google Web fonts that do support Hanyu Pinyin with tone marks:
Serifs

  • EB Garamond (227 KB)
  • Gentium Basic (263 KB — and about the same for each of the three accompanying styles: italic, bold, bold italic)
  • Gentium Book Basic (267 KB — and about the same for each of the three accompanying styles: italic, bold, bold italic)
  • Neuton (56 KB — and about the same for each of the five accompanying styles: italic, bold, light, extra light, extra bold)

screenshot of the Pinyin fonts above

Note:

  • Neuton has relatively weak tone marks, so I wouldn’t recommend it for Web pages aimed at beginning students of Mandarin.

Sans Serifs

  • Andika (1.4 MB)
  • Ubuntu (350 KB) — available in eight styles

screenshot of the Pinyin fonts above

Some Ubuntu sample PDFs: Ubuntu regular, Ubuntu italic, Ubuntu bold, Ubuntu bold italic, Ubuntu light, Ubuntu light italic, Ubuntu medium, Ubuntu medium italic.

Andika sample PDF.

Note:

  • Andika’s relatively large size (1.4 MB) makes it unsuitable for @font-face use because of download time. (Its license, however, would permit someone with the time and energy to crack it open and remove lots of the glyphs not needed for Pinyin, thus reducing the size.) More fundamentally, though, I don’t much like the look of it; but YMMV.

Since Google is likely to expand the number of fonts it offers, I’m including the list of all 29 faces I tried for this experiment, which should make it easier for those wanting to test only new fonts. (It is possible, however, that Pinyin support will be added later to some fonts that fail in this area now. If anyone hears of any such changes, please let me know.) Use of bold indicates Pinyin support; everything else failed.

Display Faces with Latin Extended (all fail)

  • Abril Fatface
  • Forum
  • Kelly Slab
  • Lobster
  • MedievalSharp
  • Modern Antiqua
  • Ruslan Display
  • Tenor Sans

Handwriting Faces with Latin Extended (all fail)

  • Patrick Hand

Serif Faces with Latin Extended

  • Cardo
  • Caudex
  • EB Garamond
  • Gentium Basic
  • Gentium Book Basic
  • Neuton
  • Playfair Display
  • Sorts Mill Goudy

Sans Serif Faces with Latin Extended

  • Andika
  • Anonymous Pro
  • Anton
  • Didact Gothic
  • Francois One
  • Istok Web
  • Jura
  • Open Sans
  • Open Sans Condensed
  • Play
  • Ubuntu
  • Varela

Additional resource: SIL Fonts for downloading (including the full versions of Andika and Gentium).

Taiwanese romanization used for Hanzi input method

Since I just posted about the new Hakka-based Chinese character input method I would be amiss not to note as well the release early this year of a different Chinese character input method based on Taiwanese romanization.

This one is available in Windows, Mac, and Linux flavors.

See the FAQ and documents below for more information (Mandarin only).

Táiw?n M?nnány? Hànzì sh?rùf? 2.0 b?n xiàzài (?????????? 2.0???) [Readers may wish to note the use of Minnan, which is generally preferred among unificationists and some advocates of Hakka and the languages of Taiwan’s tribes.]

source: Jiàoyùbù Táiw?n M?nnány? Hànzì sh?rùf? (?????????????); Ministry of Education, Taiwan; June 16, 2010(?) / February 14, 2011(?) [Perhaps the Windows and Linux versions came first, with the Mac version following in 2011.]

Hakka romanization used for new Hanzi input method

Chinese character associated with Hakka morpheme ng?iTaiwan’s Ministry of Education has released software for Windows and Linux systems that uses Hakka romanization for the inputting of Chinese characters.

This appears to be aimed mainly at those who wish to input Hanzi used primarily in writing Hakka, such as that shown here.

See also Taiwanese romanization used for Hanzi input method.

sources:

Pinyin pangram challenge

One of the many things I plan to do eventually is to put up some graphics of how Pinyin looks in various font faces. A Pinyin pangram would do nicely for a sample text. You know: a short Mandarin sentence in Hanyu Pinyin that uses all of the following 26 letters: abcdefghijklmnopqrstuüwxyz (i.e., the English alphabet’s a-z, minus v but plus ü).

But then I couldn’t find one. So I put the question out to some people I know and quickly got back two Pinyin pangrams.

Ruanwo bushi yingzuo; putongfan bushi xican; maibuqi lüde kan jusede. (57 letters)

and

Zuotian wo bang wo de pengyou Lü Xisheng qu chengli mai yi wan doufuru he ban zhi kaoji. (70 letters)

from Robert Sanders and Cynthia Ning, respectively.

James Dew weighed in with some helpful advice. And, with some additional help from the original two contributors and my wife, I made some additional modifications, eventually resulting in a variant reduced to 48 letters:

Zuotian wo bang nü’er qu yi jia chaoshi mai kele, xifan, doupi.

With tone marks, that’s “Zuótiān wǒ bāng nǚ’ér qù yī jiā chāoshì mǎi kělè, xīfàn, dòupí.”

I suppose xīfàn is not really the sort of thing one buys at a chāoshì. On the other hand, people probably don’t worry much about whether jackdaws really do love someone’s big sphinx of quartz, so I think we’re OK. Still, something shorter than 48 letters should be possible — though pangram-friendly brevity is more easily accomplished in English than in Mandarin as spelled in Hanyu Pinyin. As one correspondent noted:

Most of the “excess” letters are vowels. Trouble is that Chinese doesn’t pile up the consonants much. Brown, for example, takes care of b, r, w, and n, while only expending one little o…. There’s no word like string in Chinese (5 consonants; one vowel). Chinese piles up vowels: zuotian and chaoshi and doufu and kaoji all use more vowels than consonants.

I’m challenging readers to come up with more Pinyin pangrams.

But I don’t want this to be a reversed shi shi shi stunt, so let’s stay away from Literary Sinitic. And I’d prefer the equivalent of “The quick brown fox jumps over the lazy dog” to that of “Cwm fjord veg balks nth pyx quiz.” In other words, wherever possible this should be in real-world, sayable Mandarin.

One possible variant on this would be to use “abcdefghijklmnopqrstuüwxyz” plus all the forms with diacritics āáǎàēéěèīíǐìōóǒòūúǔùǘǚǜ.” (No ǖ — first-tone ü, that is — is necessary.) But that would be even more work.

Those who devise good pangrams will will be covered in róngyào — or something like that.

Happy hunting.

Key Chinese updated, adding new Pinyin features

The program Key, which offers probably the best support for Hanyu Pinyin of any software and thus deserves praise for this alone, has just come out with an update with even more Pinyin features: Key 5.2 (build: August 21, 2011 — earlier builds of 5.2 do not offer all the latest features).

Those of you who already have the program should get the update, as it’s free. But note that if you update from the site, the installer will ask you to uninstall your current version prior to putting in the update, so make sure you have your validation code handy or you’ll end up with no version at all.

(If you don’t already have Key, I recommend that you try it out. A 30-day free trial version can be downloaded from the site.)

Anyway, here’s some of what the latest version offers:

  • Hanzi-with-Pinyin horizontal layout gets preserved when copied into MS Word documents (RT setting), as well as in .html and .pdf files created from such documents.
  • Pinyin Proofing (PP) assistance: with pinyin text displayed, pressing the PP button on the toolbar will colour the background of ambiguous pinyin passages blue; right-clicking on such a blue-background pinyin passage will display the available options.
  • Copy Special: a highlighted Chinese character passage can be copied & pasted automatically in various permutations.
  • Improved number-measureword system: it now works with Chinese-character, pinyin and Arabic numerals.
  • Showing different tones through coloured characters (Language menu under Preferences).
  • Chengyu (fixed four character expression) spacing logic: automatic spacing according to the pinyin standard (Language menu under Preferences).
  • Option to show tone sandhi on grey background (Language menu under Preferences).
  • Full support of standard pinyin orthography in capitalization and spacing.
  • Automatic glossary building.

Some programs, such as Popup Chinese’s “Chinese converter,” will take Chinese characters and then produce pinyin-annotated versions, with the Pinyin appearing on mouseover. Key, however, offers something extra: the ability to produce Hanzi-annotated orthographically correct Pinyin texts (i.e,, the reverse of the above). If you have a text in Key in Chinese characters, all you have to do is go to File --> Export to get Key to save your text in HTML format.

Here’s a sample of what this looks like.

B?n bi?ozh?n gu?dìngle yòng? Zh?ngwén p?ny?n f?ng’àn? p?nxi? xiàndài Hàny? de gu?zé? Nèiróng b?okuò f?ncí liánxi? f?? chéngy? p?nxi?f?? wàiláicí p?nxi?f?? rénmíng dìmíng p?nxi?f?? bi?odiào f?? yíháng gu?zé d?ng?

Basically, this is a “digraphia export” feature — terrific!

If you want something like the above, you do not have to convert the Hanzi to orthographically correct Pinyin first; Key will do it for you automatically. (I hope, though, that they’ll fix those double-width punctuation marks one of these days.)

Let’s say, though, that you want a document with properly word-parsed interlinear Hanzi and Pinyin. Key will do this too. To do this, a input a Hanzi text in Key, then highlight the text (CTRL + A) and choose Format --> Hanzi with Pinyin / Kanji-Kana with Romaji.

In the window that pops up, choose Hanzi with Pinyin / Kanji-kana with Romaji / Hangul with Romanization from the Two-Line Mode section and Show all non-Hanzi symbols in Pinyin line from Options. The results will look something like this:

GIF of a screenshot from Key, showing an interlinear text with word-parsed Pinyin above Chinese characters. This is an image of the text after being pasted into Microsoft Word.

This can be extremely useful for those authoring teaching materials.

Furthermore, such interlinear texts can be copied and pasted into Word. For the interlinear-formatted copy-and-paste into Word to work properly, Key must be set to rich text format, so before selecting the text you wish to use click on the button labeled RT. (Note yellow-highlighted area in the image below.)

screenshot identifying the location of the button that needs to be pressed to make the text RTF