User:Bluedwarf/Asian Phonetic Guide

Abstract

OpenOffice.org Writer has a function for asian phonetic guide, so-called ruby, for Chinese and Japanese, which allows you to add annotative ruby characters to a corresponding Kanji string. To enter ruby on OpenOffice.org Writer, you usually open Asian Phonetic Guide dialog, however, this dialog is a little bit inconvenient.

In this page, first, the background and details of current inconvinience in that dialog are explained. Second, we look into the equivalent feature of other Office suites. At the end, some ideas for improvement of OpenOffice.org are discussed.

Background

OpenOffice.org has a good ability to split Japanese text into grammatical segments even though Japanese text doesn't have spaces between words. This separation process is doen by OpenOffice.org without user intervention. Yet this automatical separation sometimes fails due to complexity and ambiguity of the grammar. It sometimes separates text in wrong position or position which you don't expect. Unfortunately, this problem is essentially (probably) unresovable.

As a result, when you edit ruby text, you may encounter some kinds of inconvinience becase incorrectly split segments are shown in Asian Phonetic Guide dialog, which is described below.

Problems

Integration

If OOo generates smaller segments than you expect, you would try to merge two or more segements into one. However, there is not a good solution for integration of segments.

For example, here is a word "国際連合貿易開発会議" which means UNCTAD in English. Now let's try to add ruby to this word in OpenOffice.org 3.1 Writer. You will get the same result shown in the picture below. As you see, this word are recognized as the combination of 5 words, while you consider it as 1 word.

Then, to combine them into one segument, you would cut the last 4 parts and paste them together into the top text box like the picture below.

This operation results in an unexpected situation like the picture below. The 4 parts you cut and pasted would be duplicated.

Of course, there is one simple workaround that you only delete the duplicated parts, but this is quite inconvinient. It would be especially troublesome when you have a lot of wrongly separated seguments in one document.

Separation

In contrast, OOo sometimes generates longer segments than you expect. In this case, you would try to separate into a couple of segments.

For example, here is a word "東京都" which means Tokyo Metropolis. Now try to add ruby to this word in OpenOffice.org Writer. You will get the same result shown in the picture below. As you see, this word is recognized as 1 word.

However, in some conditions, you might want to separate this word into 2 parts.

To do so, you have to close Asian Phonetic Guide dialog once, select the first part and open the dialog to add ruby, and do the same thing for the second part, but you would think that this is a quite annoying operation.

Competitors

Microsoft Office Word 2003

This is Furigana dialog of Microsoft Office Word 2003. When you try to add ruby text to the Japanese text "国際連合貿易開発会議", then you will see the following picture.

As you see, it results in the similar seperation to OpenOffice.org Writer, but you can see some ruby strings are already inserted, which is one different point. Microsoft Office Word 2003 has a function, which not only separates text into seguments but also suggests ruby text automatically.

Anyway, now here you try to integrate the seperated 5 words into one. In this case, you can do that only by clicking the button "文字列全体", and you will get the correct result shown below.

Suggestion

Automatical suggestion of ruby

It would be wonderful if OpenOffice.org gave ruby for Japanese text automatically. It could be realized with the help of MS-IME like Japanese_Reconversion or morphological analyzer like MeCab library. OpenOffice.org could suggest ruby by filling out the ruby text entries in Asian Phonetic Guide dialog. This would be very helpful to add ruby. What you have to do would be to correct only wrong sugements. You could leave accurate seguments as suggested.