summaryrefslogtreecommitdiff
path: root/japanese/p5-Text-MeCab/pkg-descr
diff options
context:
space:
mode:
authorCheng-Lung Sung <clsung@FreeBSD.org>2006-07-31 03:23:19 +0000
committerCheng-Lung Sung <clsung@FreeBSD.org>2006-07-31 03:23:19 +0000
commit4dc74a6a23ad94a91dc26a93563ced520a80f422 (patch)
treeca3fb9b383c48f621aba441a8ebb1a631481fbae /japanese/p5-Text-MeCab/pkg-descr
parentAdd p5-POE-Component-Client-Telnet 0.06, a POE component that provides (diff)
Add p5-Text-MeCab 0.12, alternate Interface To libmecab.
PR: ports/101039 Submitted by: TAOKA Fumiyoshi <fmysh at iijmio-mail.jp>
Notes
Notes: svn path=/head/; revision=169171
Diffstat (limited to 'japanese/p5-Text-MeCab/pkg-descr')
-rw-r--r--japanese/p5-Text-MeCab/pkg-descr10
1 files changed, 10 insertions, 0 deletions
diff --git a/japanese/p5-Text-MeCab/pkg-descr b/japanese/p5-Text-MeCab/pkg-descr
new file mode 100644
index 000000000000..f459a3e7badf
--- /dev/null
+++ b/japanese/p5-Text-MeCab/pkg-descr
@@ -0,0 +1,10 @@
+libmecab (http://mecab.sourceforge.ne.jp) already has a perl interface
+built with it, so why a new module? I just feel that while a subtle
+difference, making the perl interface through a tied hash is just...
+weird.
+
+So Text::MeCab gives you a more natural, Perl-ish way to access
+libmecab!
+
+Author: Daisuke Maki <dmaki@cpan.org>
+WWW: http://search.cpan.org/dist/Text-MeCab/