Resource ID | Resource Type | Description |
0 | 'CSTR' | Language name |
entry ID | 'CSTR' | Your string |
1 | 'LONG' | Language ID |
2 | 'LONG' | Number of bytes of largest string |
0 | 'TEXT' | Author |
When you use Blithe, you will usually want to create your own dictionary files with Blithe Edit. These files are called application dictionaries. Each language that your application supports gets it's own application dictionary. In order to support add-ons, Blithe allows multiple application dictionaries for the same language.
Dictionaries now have an Author field. This is just plain text where you can store an authoring credit. It is used by Blithe Edit and is not accessible through the Blithe API.
Blithe provides a core set of common dictionary files. These files contain strings that are frequently used throughout the system. They are kept in /boot/home/config/etc/Blithe and are shared by all Blithe-aware applications. There are a couple of advantages in using the common dictionaries.
1. | Applications that only use entries in the common dictionaries do not need to provide their own dictionaries. |
2. | A central set of strings promotes a consistant terminology that end users can associate with certain behaviour. |
You do not need to include the contents of these files in your application dictionaries in order to use them. Blithe will automatically look in these files for your string if it is not found in your dictionaries.
There is a disadvantage in keeping your text separate from your application: it makes it easier for the user to inadvertantly break it by removing the files that your application depends on. You can make your application work as a stand-alone by doing a couple of things:
1. | Use the static library blithestatic.o in Blithe Installation/Blithe SDK/Static It will allow your application to work without blithe.so being present on the user's system. |
2. | Create a special dictionary that has a complete list of entries, including any entries from the common dictionaries. Add this dictionary to your project. Blithestatic.o will use the strings built into your application as a last resort. |