Issue 76536 - New external component: mecab
Summary: New external component: mecab
Alias: None
Product: Internationalization
Classification: Code
Component: i18npool (show other issues)
Version: current
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-04-20 07:33 UTC by bluedwarf
Modified: 2017-05-20 11:13 UTC (History)
4 users (show)

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

Attachments for new external module. (1.32 KB, text/plain)
2007-04-20 07:36 UTC, bluedwarf
no flags Details
prj/build.lst for new external module. (50 bytes, text/plain)
2007-04-20 07:37 UTC, bluedwarf
no flags Details
prj/d.lst for new external module. (186 bytes, text/plain)
2007-04-20 07:38 UTC, bluedwarf
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description bluedwarf 2007-04-20 07:33:24 UTC
The request for new external component, mecab.
Please see i74034 for the purpose of this component.
Comment 1 bluedwarf 2007-04-20 07:36:51 UTC
次の添付ファイルを作成しました。 (id=44554) for new external module.
Comment 2 bluedwarf 2007-04-20 07:37:24 UTC
次の添付ファイルを作成しました。 (id=44555)
prj/build.lst for new external module.
Comment 3 bluedwarf 2007-04-20 07:38:09 UTC
次の添付ファイルを作成しました。 (id=44556)
prj/d.lst for new external module.
Comment 4 bluedwarf 2007-04-20 07:44:06 UTC
To make "macab" module available, these uploaded files must be located in new
top level directory "mecab" and mecab-0.94.tar.gz must be located in

mecab-0.94.tar.gz is available from
Comment 5 ooo 2007-04-20 13:50:05 UTC
Hi Takashi,

Thanks for the build system integration. However, we should only add it if the
legal process for mecab is solved, I'm Cc'ing Martin 'mh' for this. In issue
74034 you mentioned you followed the steps lined out at so this task just takes over from that issue.

Btw, note that the 'hedabu' directive in d.lst was reserved for OOo internal
code and now is outdated and was removed for m209. External modules should
simply copy needed headers to the solver subdirectory. The directive
mkdir: %_DEST%\inc%_EXT%\mecab
is missing, which creates the subdirectory for the header files to be delivered.

Did you try to compile and use mecab on other platforms as well? Especially
Windows and Solaris would be needed before we could integrate it into regular

Comment 6 bluedwarf 2007-04-21 02:43:47 UTC
legal issues:
According to the steps at the top page of external project, I've already send a
form about "mecab". Now I'm just waiting the reply.

'hedabu' directive:
All right. I'll create another patch.

platform problems:
Sorry, I've never tried to compile mecab on neither Solaris nor Windows. Since
we can find some blogs mention that mecab works on Solaris and Windows, it
doesn't seems to be impossible. So I'll try it after we solve the legal issues.
However, it may take long time because I don't have build environment for
Solaris and Windows and I have to construct it first.
Comment 7 ooo 2007-04-24 16:55:09 UTC
Hi Takashi,

> The new patch doesn't link to system library but depends on
> generated by new top level module "mecab". See i76536 for details of the
> new module.

I'm not sure if that's such a good idea. Doing so lets depend this issue
on issue 76536 and the presence of the external mecab module within OOo,
regardless of the outcome of the legal things, whereas until now it was
possible to optionally build OOo with mecab anyway. Instead, a configure
switch could determine whether to use mecab and/or which one to use,
system or OOo mecab.

Comment 8 Marcus 2017-05-20 11:13:40 UTC
Reset assigne to the default "".