80b0a3a7b6
It's too small to justify standalone existence. We can accumulate i18n things we link to directly into i18nutil and rework i18npool uno implementions in terms of thin wrappers over i18nutil and prefer linking to i18nutil internally and leave the uno forwarders for use by external components and scripting |
||
---|---|---|
.. | ||
inc/i18nutil | ||
prj | ||
source/utility | ||
Library_i18nutil.mk | ||
Makefile | ||
Module_i18nutil.mk | ||
Package_inc.mk | ||
README |
i18nutil is internalization related utilties It comprises of honest c++ code which you just link to directly, while i18npool tends to consist of code you interact with via uno.