Glad to hear from you again. I recognized your name as soon as I saw it.
What you're saying sounds possible, but I'm not sure it's necessary. I've never noticed that using
ISO-8859-1 corrupts Windows files. Can anyone out there tell me if I'm wrong about that?
Unfortunately, if you decide you want this change, you'll probably have to implement it yourself.
I really can't make any promises at this point about when I'll (finally) get around to developing
new SJ functionality.
> Hello, Robert!
> It's been a while since my last e-mail. I'm the one who did that
> little translation tool, ages ago...
> Now I'm back, and have a little question for you: Is it possible for
> SJ to use different encoding charsets for differente files? I had
> configured SJ server to store text files in UTF-8, since most of my
> files are on Linux, and are UTF-8. Now I need to store some Delphi files
> and it seems that these files are ISO-8859-1.
> Well, my big problem is that this situation forces SJ to be mutually
> exclusive regarding the charsets. That is, I can either store using
> UTF-8 and have my Windows files corrupted or store using ISO-8859-1 and
> corrupt my Linux files. I thought of setting up two servers, but that
> would be too much of a hammer solution, and I'm trying to avoid that.
> I can think of three possible solutions for this:
> 1) SJ could use a specific encoding charset (utf8 or iso8859-1) for
> storing the text file, but also storing what encoding the user wants the
> file to use. This way, during the Get SJ would convert the file
> between the storage and user charsets.
> 2) SJ could store each file it its own encoding charset, eliminating
> the need of conversion.
> 3) Combine the two above: SJ would store the file on its own
> encoding, but also allow conversion (other users might want the file
> with a different encoding).
> I hope you can help me find a solution for this problem.
> Marcelo Saldanha
> Ciência da Computação - UFMG