|
Thank you for your extremely long-winded albeit completely useless post. I am fully aware of how computers store information and I am fully aware of what CCSID's are and how they work. What I don't understand is how seu can properly render file members of different CCSID's (sda can do this too) while WDSC, a purportedly superior product to seu, cannot. Client access a\has nothing to do with this and I if the only way to make this work is to have one pc configured in Japanese and one in English then the solution is absolutely unacceptable. WDSC should be able to translate the member I want to open based on the CCSID of the file that contains it. I thought that maybe someone on this board would have met this challenge before me and found a solution or at the very least I wanted someone on the WDSC development team to become aware of the problem. Thank you Chris
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.