Rubies dialog is not fully functional.

Japanese language support is on.

User enters text in Japanese, and selects it.

User invokes "Format/Asian phonetics guide..." from menu.

What's supposed to happen is that the software identifies kanji word stems
("base text") in the selected text, and puts them one to each box in the "base
text" column of the dialog box, and in the right-hand column, it should insert
the furigana ("ruby text") for each base text item. The user can edit them by
inserting an alternative pronunciation, or by deleting the furigana for some
items.  Then the user clicks "Apply", and rubies (furigana) are applied to all
the word stems accordingly.

There are several ways in which this doesn't work properly in OOo:

1) Instead of picking up just word stems, it picks up whole words as they appear
in dictionaries, so if you write 行きます, (ikimasu -- the present or future
tense of "to go"), it picks up 行き, (iki -- the gerund of "to go"), when it
should pick up 行, (i -- the stem of "to go"). It leads to incorrect positioning
of furigana. Picking up only word stems shouldn't be hard from the programming
point of view, since they are sequences of kanji characters, and can be
identified by the simple expedient of checking the unicode value of the
characters to see if they are in the range of kanji characters, as opposed to
kana, space, punctuation, or some other (or by using a dictionary subset that
contains only kanji stems, no inflected forms or words spelled in kana).

2) The software doesn't produce the furigana, so the user has to type them all
in by hand. From the way the software picks up words for the "base text" fields,
it is evident that it is using a dictionary. If that dictionary contains entries
for the pronunciation of each word contained therein, it ought to be a small
matter to look up the pronunciation and insert that into the associated "ruby
text" field. Sadly, the software doesn't bother, and the user is left with the
tedious job of doing it by hand. In some situations, this could involve looking
up a separate dictionary.

3) The system is completely fooled by punctuation marks. If the user selects an
area of text that includes a comma (、), full-stop (。), or other punctuation
mark, all the rest of the selected area, including the punctuation mark will be
inserted into a single ruby text field. This adds to the tedium of adding
furigana to text, because only one phrase can be handled at a time, rather than
a substantial passage of text being all handled at once with a single invocation
of the dialog.

4) The software ought to remember the furigana entered by the user, so that it
can be automatically used again the next time the pronunciation guide dialog box
is invoked.

If the ruby dialog were fully functional, a user could select a whole page of
text, invoke the phonetics guide once, click "Apply", and see furigana for all
the words in passage. As it stands now, the user would have to invoke the dialog
dozens of times, and type in the pronunciation for each word by hand, in a
procedure more tedious than it would be to type out the whole passage twice,
once with kanji and once without.