hanyl05 wrote:It’s great that Goldendict finally supports image files in stardict format dictionaries.
Currently the supported image files must be named in a res folder.
But it would be better if Goldendict can support image files in a zip format, such as named res.zip.
For some dictionaries, especially for encyclopedia, usually there are thousands of image
Anyhow, it’s really great that the support for stardict is nearly perfect. Many thanks to developers!
Although possible we will divert from the Standard format. The format specification clearly states that you should use a resource storage for media:
"Resource Storage store the external file in 'r' resource file list, the
image in html code, the image, media and other files in wiki tag.
It have two forms:
1. Direct directory and files in the "res" sub-directory.
2. The res.rifo, res.ridx and res.rdic database.
Direct files may have file name encoding problem, as Linux use UTF-8 and
Windows use local encoding, so you'd better just use ASCII file name, or
use databse to store UTF-8 file name.
Databse may need to extract the file(such as .wav) file to a temporary
file, so not so efficient compare to direct files. But database have the
advantage of compressing.
You can convert the res directory and the res database from each other by
the dir2resdatabse and resdatabase2dir tools.
StarDict will try to load the storage database first, then try the direct
The format of the res.rdic file:
It is just the join of each resource files.
You can dictzip this file as res.rdic.dz"
GoldenDict currently only supports option 1 for resources in stardict dictionaries.