path: root/i18npool/README
diff options
authorTor Lillqvist <>2014-04-14 14:31:25 +0300
committerTor Lillqvist <>2014-04-14 17:21:19 +0300
commit0b6fb1f45a179e94bb39f49dd8f245812d753113 (patch)
tree5e697160e3c5e1cfa4a11057b2dd72c77f49f83d /i18npool/README
parentc0f2dc1347cfbc121408959531998b217cd1c617 (diff)
Put the dict_ja and _zh data in files instead of code for iOS
Map the file(s) into memory on demand. The executable file of an app needs to be as small as possible. Including additional data files in an app bundle is fine. Change-Id: Ife9bfe99a2cf0473d459f38f50dfa3304b39e282
Diffstat (limited to 'i18npool/README')
1 files changed, 14 insertions, 1 deletions
diff --git a/i18npool/README b/i18npool/README
index 86f72d1babe2..9e1a04f3f329 100644
--- a/i18npool/README
+++ b/i18npool/README
@@ -1,6 +1,19 @@
Internationalisation (i18npool) framework ensures that the suite is adaptable to the requirements of different
-native languages, their local settings and customs, etc without source code modification.
+native languages, their local settings and customs, etc without source code modification. (Wow, that is such marketing-speak...)
Specifically for locale data documentation please see i18npool/source/localedata/data/locale.dtd
See also []
+On iOS we put the largest data generated here, the dict_ja and dict_zh
+stuff, into separate files and not into code to keep the size of an
+app binary down. Temporary test code:
+ static bool beenhere = false;
+ if (!beenhere) {
+ beenhere = true;
+ uno::Reference< uno::XComponentContext > xComponentContext(::cppu::defaultBootstrap_InitialComponentContext());
+ uno::Reference< lang::XMultiComponentFactory > xMultiComponentFactoryClient( xComponentContext->getServiceManager() );
+ uno::Reference< uno::XInterface > xInterface =
+ xMultiComponentFactoryClient->createInstanceWithContext( "", xComponentContext );
+ }