Please ... Have you fixed the bug related with i18n ?

I hadn't really considered internationalisation when I first designed dbFM (despite the fact that my company - eserv - operates worldwide) .
I'm afraid the answer is that there is no quick fix for this module. There are several places in the drupal code where I've missed using the t function but that's relatively quick and easy to fix. However there's a lot of text in the javascript code and it would take longer to find an elegant solution that dealt with returning the correct text
Plus I'd need someone to help me check the translations once they were finished. I'm guessing at a full week's work total for the first language (much less for each successive language).
Eserv's priority at the moment is getting effective searching rather than internationalisation so I can't see it happening in the near future.
After searching there's 'subscribing' and email notification when a document is changed. Possibly internationalisation would come after that?