┘SUS╣y

*** Reply to a message from ZX.TALKING (Free communication of spektrumists). Hello Kirill! 31 Dec 00 04:55, Kirill Frolov -> Eugene Palenock: KF> XLATIMPORT IBMPC KF> XLATEXPORT IBMPC KF> XLATCHARSET CP1125 KOI8-R ibm_koi.chs KF> XLATCHARSET UKR KOI8-R ibm_koi.chs And this is not 866 encoding, there are differences in the codes F2h..FEh KF> Since I use koi-8 in my system, and messages in Fido KF> is usually in 866 encoding, then I have to use conversion in KF> goldede. I can recode all letters during the tossing process, but KF> I don’t want to - there will be even more problems. So every time I don't have KF> charset is entered, I see the text is not recoded, in koi-8 and I go into the config KF> goldeda add a new line. What comes from and where it recodes here KF> I hope it’s clear - everyone writes exclusively in 866 encoding, and the CHRS kludge KF> they put it out of the blue. Don't you think that XLATIMPORT is the default table for those who don't kludge? did you put it? I thought so too, and then I discovered that GED is first of allunpacks Quoted-Printable encodings, secondly it ignores XLATCHARSET. Moreover, I don’t understand the logic yet, but it searches for a substring of the name of arbitrary length tables in other table names, and if it finds it, it does not allow you to include another table. In general, some kind of insanity, but the author (Aganichev) answered me that this is really so, it’s still from the branded version, and he doesn’t really know algorithm. He said it had something to do with LATIN-1-QP And practically - this doesn’t work, it turns on instead of both, only the first table. Even forced selection by Ctrl-J XLATCHARSET WIN+K8R CP866 WK_866.chs XLATCHARSET WIN+K8R+H CP866 WKH_866.chs And this is how it all works: XLATCHARSET WIN+K8R+H CP866 WK1_866.chs XLATCHARSET WIN+K8R CP866 WK2_866.chs Best regards, Evgeniy.