Currently, I'm seeing that MozillaTraslator 4.31 is "spamming" my C:\WINDOWS\TEMP directory with MT_xxxxx.tmp files and never deleting them. I hate having TEMP directory filled with 200 of that files (size is a bit over 500 KB but they're actually using almost 1.2 MB of disk space), couldn't MT just kill those files on exit?

I haven't looked in the code, but there's the possibility to file.deleteOnExit() or somesuch. But I can't belive Henrik just forgets to delete these, I suspect another problem. I'm just experiencing this in another project where temp files are supposed to be deleted with file.delete() which works on UNIX but simply fails on Win. If that's the case, I'm very eager to get to know a solution :)

I have just done a small review of the code, and yes I do use file.delete when I'm finished with the individual files. I do see the MT_* files on my system too, so this bug is confirmed I will try to use a file.deleteOnExit or something to fix the problem.

I've noticed (form the sound of my HDD) the flushing in TEMP of MozTranslator occurs usually when you try to edit an "unknown file type" (html, css, ..). The bad, is this won't happen every time (seldom luckily). This is just an impression, may be Java won't accept long files on grid fields ? Couldn't be sobstituted the grid pane with the editing window (as a child window) ?

I'm not sure what you are referring to with the grids and files ? can you explain in more details ?

Henrik, do you still use that account? anyway, MT5 is working quite good on Linux, it seems: I got 4500 MT_*.tmp files in my /tmp/ right now! This bug is alive!

yes i use this account :-) adn damm, I ask it to delete when existed, but I guess linux don't

removeing dependency, MozillaTranslator is a seperate program, and the mozilla bug is unrelated

I will look at this for beta 9

retargeting

this should have been fixed in 5.00 final, someone please verify

The MozillaTranslator component is moving to the Mozilla Localisations product.

Can someone try to verify this one? I still have this problem as listed in Comment #5 on Linux :( Currently using MT 5.02 I gues I'll have to REOPEN :(((