Hi,
I just converted the babylon dictionary .bgl to .ifo. there are three files just like you said. .dict, .idx, .ifo. I copied them to /usr/share/stardict/dic/ and created a folder for them. but I can not find it in the stardict. I found the other dictionaries which are from the stardict contain a file .dz. why I do not have that file after converting?

Hi Eric,
it is correct that you do NOT have a .dz file. You are supposed to have exactly what you said, that is a .dict, .idx, .ifo. The .dict will do the same that the .dz does
Create a folder for *each* dictionary. Restart Stardict, go to “manage dictionaries” (bottom right, the button with the “i”) and you should see them there. For me it worked perfectly on all of my machines, i have Stardict 2.4.8 on opensuse 11

Hello
I’m a Windows user, apparently this tutorial is for Linux. Is there a similar way to convert babylon dictionaries to these .ifo files useful in StarDict? I downloaded Stardict and dictconvert, but then I’m stuck. Can you help me? Thanks a lot. Michiel

hi Michiel, yes the tutorial above is for Linux only, pretty much everything you can find on this website applies to Linux only because this is Opensuse website and Opensuse is a Linux distro.
I have no idea how to do that in Windows as i barely ever use windows systems, anyway i think your best bet is googling it, or use babylon directly, since you are in windows you can do that, the rationale behind this tutorial is that there is no babylon software for linux

Ciao Rossana,

Vorrei utilizzare i dizionari Babylon (che sono i migliori come hai anche detto tu) che uso su Windows con l’applicazione Dictionary su Leopard (MacOS 10.5).
Essendo un programmatore su piattaforma Apple (e Windows ma non Linux… I’m sorry) ho scaricato i sorgenti e li ho compilati applicando alcune semplici correzioni al makefile per risovere alcuni problemi di link con libiconv.
Il programma si compila e si installa correttamente ma quando provo a eseguire la conversione dei dizionari l’applicazione va in Segmentation Fault.
Prima di imbarcarmi nel debug del codice volevo sapere se, per caso, avevi qualche idea su cosa non funzioni compilando su Mac che come probabilmente sai e’ uno stretto derivato di Unix (BSD). Magari qualcuno che lo ha gia fatto sul Mac te lo ha detto e poi chiedere non costa nulla… almeno spero
Ti ringrazio e scusa per il disturbo.

Un saluto dalla Silicon Valley.

Luca

Hello Luca,
i reply in English just in case this might be useful to someone else

It is virtually impossible to say what is not working on a Mac. I do not have any Macs so i cannot test. It could be one million different things. Mac is derived from Unix sure, but in general applications and source codes cannot be swapped between them as there are many inherent difference in the OS structure, libraries, etc. One application designed for Mac is not generally portable on a Linux, and vice versa. There might be some exception of source code that is platform independent such as Java but i think this application is not one of those.

I would suggest two things:
1) you can install the dictionary converter on any linux system, if you do not have you could ask a friend to do so for you, then convert the dictionaries and bring to your computer only the converted dictionaries. That’s what you need, you actually do not need the converter itself on your computer.
2) if you really cannot find anyone around you, willing to help and running a linux, you could at least use a debugger to locate the cause of the segmentation fault, otherwise without a debugger i guess it is a real hell.

How many dictionaries do you need to convert? If they are not too many i could do it for you, and upload somewhere or email to you the converted dictionaries

Let me know, if i can help i will be glad to

Rossana

Just what I was looking for!, dictconv works great on kubuntu hardy
thx thx thxthxthx