Ports Search

dbskkd-cdb is a dictionary server for the SKK Japanese input method system. dbskkd-cdb is based on the code of skkserv (the original SKK server) 3.9.3, using the cdb constant database package of D. J. Bernstein (DJB) for faster dictionary access. dbskkd-cdb is compatible with skkserv on the protocol behavior. It is called from "super-server" programs such as inetd or tcpserver, and the I/O operation is solely with the stdio interface, so the code is compact and the access to the server can be easily restricted.

Esecanna pretends to be a cannaserver and listens to canna clients. It interprets to one of the VJE 3.0/2.5 or Wnn6 servers what they say, then passes through to them what it results. You'll have to install one of the esecanna modules to run it. With this, you can use VJE 3.0/2.5 or Wnn6's smart input engine also from the console applications. [ canna clients ] (mule, jvim, etc.) || /\ \/ || [ esecanna ] (esecannaserver + {vje30,wnn6} module) || /\ \/ || [ input engine ] (vjed or jserver) Further information is found on the following web site:

Epwutil contains following utilities: bookinfo - view a component of the book to know how to downsize it. catdump - edit and concatenate the CD-ROM catalogue files. squeeze - remove multi-media data(image or audio) and indexes for conditional or compound search from the book. Bookinfo and squeeze can not be used for EPWING V4 and later. See "Section 5: Restriction" in epwutil.doc. In use of this programs, you have to check the agreement of your CD-ROM books on making copies or modifying books for personal use. See "Section 2: Before using epwutil" in epwutil.doc.

jacode.pl - Perl library for Japanese character code conversion This software has upper compatibility to jcode.pl. * jcode.pl upper compatible * Perl4(also Perl5) script * Acts as a wrapper to Encode::from_to (Yes, not only Japanese!) * Support HALFWIDTH KATAKANA * Support UTF-8 by cp932 to Unicode table http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP932.TXT http://support.microsoft.com/kb/170559/ja (JIS X 0221:2007 BASIC JAPANESE and COMMON JAPANESE) * Hidden UTF8 flag * No Object oriented * Possible to re-use past code and how to

KON2 is a program for displaying Kanji (japanese characters) on the console of Linux/FreeBSD. KON2 hooks the output of console and redirects to pseudo tty, drawing on the VGA display. If KON2 would be going to something wrong, check shared-memories being loading or not. If not, add "options SYSVSHM" to /usr/src/sys/i386/conf/GENERIC, and reconfigure the kernel. Be aware that using KON2 with X is not allowed (You should shutdown X first when you use KON2, and vice versa). In order to use 30 lines (default is 25), modify the "Normal" entry of kon.cfg as follows: ------- VGA:Normal VGA 640 680 768 800 480 491 493 525 1 79 29 -------

migemo.el is a Japanese incremental search tool for Emacs. You can search Japanese words on Emacs without Kanji conversion. This migemo.el is forked version from the original one bundled with migemo. To use migemo.el, please set the following elisp to your own ~/.emacs.d/init.el file. (require 'migemo) (setq migemo-command "cmigemo") (setq migemo-options '("-q" "--emacs")) (setq migemo-dictionary "/usr/local/share/cmigemo/utf-8/migemo-dict") (setq migemo-user-dictionary nil) (setq migemo-regex-dictionary nil) (setq migemo-coding-system 'utf-8-unix) (load-library "migemo") (migemo-init)

Kterm is a xterm replacement with Japanese (Kanji) support. It also understands ANSI color sequences. This version is 6.2.0, available from the X11R6 contrib tape. Also included is support for Xaw3d arrow-style scrollbars and neXtaw NeXT-style scrollbars. You can now hold down the arrow buttons to scroll continuously. And also included kterm background-wallpaper patch. This patch is made by Junji Takagi <takagi@an.ip.titech.ac.jp>, and revised by Takuji Iimura <uirou@mma.club.uec.ac.jp>. Finally, this port is made by Satoshi Asami <asami@cs.berkeley.edu>, and revised by Shigeyuki Fukushima <shige@FreeBSD.ORG>.

The Discovery Component is about discovering, or finding, implementations for pluggable interfaces. It provides facilities instantiating classes in general, and for lifecycle management of singleton (factory) classes. Fundamentally, Discovery locates classes that implement a given Java interface. The discovery pattern, though not necessarily this package, is used in many projects including JAXP (SaxParserFactory and others) and commons-logging (LogFactory). By extracting this pattern, other projects can (re)use it and take advantage of improvements to the pattern as Discovery evolves. Discovery improves over previous implementations by establishing facilities for working within managed environments. These allow configuration and property overrides without appealing to the global System properties (which are scoped across an entire JVM).

The Sigar API provides a portable interface for gathering system information such as: * System memory, swap, cpu, load average, uptime, loginsi * Per-process memory, cpu, credential info, state, arguments, environment, open files * File system detection and metrics * Network interface detection, configuration info and metrics * TCP and UDP connection tables * Network route table This information is available in most operating systems, but each OS has their own way(s) providing it. SIGAR provides developers with one API to access this information regardless of the underlying platform. The core API is implemented in pure C with bindings currently implemented for Java, Perl, Ruby, Python, Erlang, PHP and C#. This port provides the Java bindings.

XDoclet is a Java code generation engine. It enables Attribute-Oriented Programming for java. In short, this means that you can add more significance to your code by adding meta data (attributes) to your java sources. This is done in special JavaDoc tags. XDoclet will parse your source files and generate many artifacts such as XML descriptors and/or source code from it. These files are generated from templates that use the information provided in the source code and its JavaDoc tags. XDoclet lets you apply Continuous Integration in component-oriented development. Developers should concentrate their editing work on only one Java source file per component.