Issue 37606 - Automatic ruby for Japanese
Summary: Automatic ruby for Japanese
Alias: None
Product: Internationalization
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial with 3 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2004-11-22 10:23 UTC by bibiko
Modified: 2016-12-03 17:40 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description bibiko 2004-11-22 10:23:14 UTC
Dear all,

my name is Hans-Joerg Bibiko and I work as a computer linguist. My main topic is
the generel data processing of non-latin writing scripts like Chinese, Japanese,
Tibetan, Korean etc. 
Together with Ulrich Apel and a lot of volunteers we're writing a huge and open
Japanese-German Dictionary (ca. 215.000 entries;
My question is whether it would be possible to integrate a Japanese-English (by
Jim Breeen) and a Japanese-German dictionary into the OO (maybe also my
Kanji-Database of 12168 Kanji ( It should also be possible
to add these lemmata as references for a automatic ruby suggestion of Japanese
kanji composita, i.e. I select a paragraph and for all kanji the plugin looks
for ruby text as hiragana, katakana or roomaji (Hepburn, Kunreishiki)
Furthermore, with the help of my databases, to enhance the ability to write
Japanese with kanji variants, etc.

all the best 

Comment 1 stefan.baltzer 2004-11-22 20:26:00 UTC

It is possible. You have to find volunteering developers in the OOo community 
interested in doing so. Otherwise this Enhancement request will probably 
get "very old". AFAIK, no other Office suite features dictionaries yet.  
Therefore I think that our (SUNs) developers will NOT start a project like this 
in the foreseeable future.

A possible solution is to set up a "stand-alone" solution that can be attached 
to the the Office later on. A good example for a stand-alone feature that later 
makes it into OOo is the WordPerfect filter.

When asking for Features or Enhancements, it is always recommenable to 
propose "tiny chunks" within an issue. Your Summary does not tell about a 
translation feature. Beware of so-called "collective tasks"!

It may be possible to describe a whole new world withi a few sentences,  but 
someone (One developer in most cases) must be able to handle such a task.

Reassigned to BH.
Comment 2 attahb 2006-07-04 11:44:10 UTC
"AFAIK, no other Office suite features dictionaries yet."

I doubt that's true. If it were, I can't see how the feature described by Hans-
Joerg Bibiko would work in Microsoft Word, but it does. You can automatically 
generate ruby suggestions for an entire document, and this feature has been in 
Word since Word 2000, at least. It must be using a dictionary.

"someone (One developer in most cases) must be able to handle such a task."

This is a project that one developer could do. The basic framework is already 
present. The "ruby" dialogue box already looks up furigana suggestions, one 
phrase at a time. All that is needed is to change the data source from which it 
does the lookup, and fix the bugs that prevent it from looking up more than one 
phrase at a time.
Comment 3 dvdkhlng 2009-04-28 12:48:13 UTC
Looks like something like this is now available via a 3rd-party extension:

Maybe sometime this can get added to mainline OOorg?  Many japanese users of M$
Word (especially teachers) are quite used to such a feature being present in the
japanese version of Word.  For them, this is a major blocker keeping them from
migrating to OOorg.

BTW while this feature is still missing: I also created a very minimal CGI
web-app to create .odt files with Furigana at .
 This one is based on the open-source Kakasi tool (

Comment 4 bettina.haberer 2010-05-21 14:38:27 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements". 
Comment 5 jd 2016-12-03 17:40:32 UTC
(In reply to dvdkhlng from comment #3)
> Looks like something like this is now available via a 3rd-party extension:
This extension does not work any more and is apparently abandoned.