Someone to use some characters built on your applications, you would make pfo file and add it on your resource of your application. For your expansion about languages of pebble, your could make language pack file and install on your pebble.
For one-byte character countries, like european languages, you need to make only one message file.
- You would download some language pack from
- unpack language pack with pbpack_tool.py
- discompile message file 000 with msgunfmt from GNU gettext utilities.
- edit 000.po (messages and language settings.)
- compile 000.po to 000.mo with msgfmt from GNU gettext utilities, and rename it to 000.
- pack language pack include new 000 file
For two-byte countries, need to install 2-byte character glyph data, you need to make pfo files with fontgen.py, and build your language pack.
- unpack some language pack with pbpack_tool.py
- (if you need to make messages on your language) discompile message file 000 and edit it like above.
- make pfo files from some truetype font to install character glyphs on your pebble: 14dot, 18dot, 24dot, 28dot / both regular and bold weight
- rename pfo file for 14dot regular -> 001
- rename pfo file for 14dot bold -> 002
- rename pfo file for 18dot regular -> 003
- rename pfo file for 18dot bold -> 004
- rename pfo file for 24dot regular -> 005
- rename pfo file for 24dot bold -> 006
- rename pfo file for 28dot regular -> 007
- rename pfo file for 28dot bold -> 008
- repack all of objects with pbpack_tool.py with pack option
then language pack would made.
But all of characters for your language cannot put on the language pack because of pebbles storage size.
So, pfo file need to limit its include characters with json list.
When you use the same pfo file in the same dot size, for example 28dot regular (filename 007)and bold(filename 008), the language pack would smaller of its size. I suppose it would be link the same glyphs in the language pack, and ignore object.