From: Gisbert R. <ru...@gr...> - 2001-07-08 17:40:43
|
Hello, in notework.txt of GoldED+ 1.1.5-0703 I found this remarks: + Implemented FSP-0013 support. You may notice warnings about obsolete codepages in your config, please fix them. If you use XLATEXPORT to obsolte codepage and this is required on some reason you may prevent error by setting USECHARSET to No. + GoldED+ now tries to set up correct values for XLATLOCALSET, XLATIMPORT and XLATEXPORT basing on your locale settings. Sorry for having the need to say a second time: That=B4s not a good idea. ;-) FSP-0013 (http://www.grudolph.de/files/ftsc/fsp/FSP-1013.Z01) is not in common use. If implemented a character set kludge is used like proposed in FSC-0054 (http://www.grudolph.de/files/ftsc/frl/FSC-0054.Z04). IPMPC is used as a synonym for codepage 437, CP437 will not be recognized by most FidoNet software. So I have to ask again to go back to the well known and accepted old behavior. --=20 Mit freundlichen Gr=FC=DFen Gisbert Rudolph |
From: Gisbert R. <ru...@gr...> - 2001-07-08 18:03:39
|
Gisbert Rudolph wrote: > Sorry for having the need to say a second time: That=B4s not a good ide= a. > ;-) FSP-0013 (http://www.grudolph.de/files/ftsc/fsp/FSP-1013.Z01) is no= t > in common use. Sorry, it=B4s FSP-1013 of course not 0013. --=20 Mit freundlichen Gr=FC=DFen Gisbert Rudolph |
From: Jesper <je...@da...> - 2001-07-08 18:53:37
|
> + Implemented FSP-0013 support. You may notice warnings about obsolete > codepages in your config, please fix them. If you use XLATEXPORT to > obsolte codepage and this is required on some reason you may prevent > error by setting USECHARSET to No. >=20 > + GoldED+ now tries to set up correct values for XLATLOCALSET, > XLATIMPORT and XLATEXPORT basing on your locale settings. >=20 > Sorry for having the need to say a second time: That=B4s not a good ide= a. I think it's absolutely great... :) > ;-) FSP-0013 (http://www.grudolph.de/files/ftsc/fsp/FSP-1013.Z01) is no= t > in common use. If implemented a character set kludge is used like > proposed in FSC-0054 There are no big differences between the two standards. FSP-1013 is merely an attempt to clarify some thing that were unclear in FSC-0054, and to suggest some new CHRS values. > IPMPC is used as a synonym for codepage 437, CP437 will not be=20 > recognized by most FidoNet software.=20 If that was the case everything would be fine, but unfortunately that is not how it is. IBMPC means CP865 in Denmark, CP866 in Russia, and in China it can mean e.g. 16-bit GB code. There might be some software that doesn't recognize CP437, but it is probably possible to make it understand the new kludge by modifying the setup or adding a new translation map. Even if it is impossible to make the program understand CP437 most software will use CP437 (or no translation) by default. I agree that this might be a small problem, but it is much better than the situation where IBMPC can mean anything. If you don't like this maybe you could do it like FDAPX and MsgEd TE is doing it; by keeping the "CHRS: IBMPC" and adding a separate "CODEPAGE: 850" kludge? //Jesper |
From: Mikael K. <mk...@ho...> - 2001-07-08 19:00:21
|
At 2001-07-08 20:53 +0200, Jesper S=F6rensen wrote: >If you don't like this maybe you could do it like FDAPX and MsgEd TE is >doing it; by keeping the "CHRS: IBMPC" and adding a separate "CODEPAGE: >850" kludge? This is what I would like to see, since programs still being developed can= =20 use the extra info in the CODAPAGE kludge at the same time old programs=20 won't break. /MiK |
From: <AAg...@ne...> - 2001-07-12 18:52:03
|
Gisbert, Gisbert Rudolph <ru...@gr...> wrote: > + Implemented FSP-0013 support. You may notice warnings about obsolete > codepages in your config, please fix them. If you use XLATEXPORT to > obsolte codepage and this is required on some reason you may prevent > error by setting USECHARSET to No. > Sorry for having the need to say a second time: That?s not a good idea. > ;-) It's a very good idea. Someone should stop investigating of new and new way of specifying any charset for anything except used one and why that should not be me? Now people should start to think what they insert in the CHRS kludge, or this will be done to the proper value by default. > IPMPC is used as a synonym for codepage 437, CP437 will not be recognized > by most FidoNet software. If this software recognizes the mail without charset (it should by the FTS, not FSC or FSP), it will ignore unknown charset and everything became OK. If not - this software should have an ability to setup additional translation, or setup default translation. Could you proove that new behaviour cause problems? ;) > So I have to ask again to go back to the well known and accepted old behavior. With the growing Linux community, amount of unreadable mails or mails with idiotic charsets are growing as well. I believe this should help in setting up the software HINT: UseCharset No XlatLocalSet IBMPC UseCharset Yes But it's a very bad idea to use this code :-P -- alexander aganichev url: http://aaganichev.narod.ru __________________________________________________________________ Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ |
From: Mikael K. <mk...@ho...> - 2001-07-12 21:19:05
|
At 2001-07-12 14:51 -0400, Alexander Aganichev wrote: >not be me? Now people should start to think what they insert in the CHRS >kludge, or this will be done to the proper value by default. Well, could you *please* at least consider to add an option to use CHRS IBMPC+CODEPAGE in GoldED+? As it is now in R20, I would guess that something like 90% of the editors in use doesn't recognize CHRS CPxxx (and I don't see any updates of the editors in question any time in the "near" future :( ). The CODEPAGE-kludge doesn't have to (and shouldn't) be the default, but it would be really nice to have support for it. ..but that's only my two cents.. =) -- ------------------------------------------------------------------- Mvh Mikael Karlsson * mk...@ho... * http://mik.nu * ICQ 650551 * ------------------------------------------------------------------- |