tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Capability mismatch between gettext-lib and gettext-tools



Hi,

Is it possible to change current strategy for using gettext-{tools,lib}?

* Current strategy

1. use builtin gettext-tools, or install devel/gettext-tools
   (depend on settings and/or builtin version)
2. use builtin gettext-lib, or install devel/gettext-lib
   (ditto)
3. prepare *.po file depending on capabilities of gettext-tools
   (strip some entries if it is not supported)

* Issues - capability mismatch between gettext-lib and gettext-tools

If gettext-tools is less capabilities than gettext-lib,
some translations may not appear well even though
its library has sufficient capabilities.
If gettext-tools is much capabilities than gettext-lib,
some translations may not be handled well by the old library.

It is not only happened with builtin one v.s. pkgsrc one.
For example, NetBSD's Citrus libintl support dcgettext(3) and
dcngettext(3), but builtin gettext-tools is too old and msgctxt
will be stripped.

* Proposed strategy
1. check capability of gettext-lib
2. if builtin gettext-tools is less capabilities than -lib,
   -tools from pkgsrc must be preferred than buitin one.
3. prepare *.po file depending on capabilities of gettext-lib
   (strip some entries if it is not supported)

--
OBATA Akio / obache%NetBSD.org@localhost


Home | Main Index | Thread Index | Old Index