…-ir-149 KS_C_5601-1989 KSC_5601 korean csKSC56011987 ISO-2022-KR ISO-2022-KR 37 RFC1557 ] (see also KS_C_5601-1987) RFC1557 ][ Woohyong_Choi csISO2022KR EUC-KR EUC-KR 38 RFC1557 ] (see also KS_C_5861-1992) RFC1557 ][ Woohyong_Choi csEUCKR ISO-2022-JP ISO-2022-JP 39 RFC1468 ] (see…

…-ir-149 KS_C_5601-1989 KSC_5601 korean csKSC56011987 ISO-2022-KR ISO-2022-KR 37 RFC1557 ] (see also KS_C_5601-1987) RFC1557 ][ Woohyong_Choi csISO2022KR EUC-KR EUC-KR 38 RFC1557 ] (see also KS_C_5861-1992) RFC1557 ][ Woohyong_Choi csEUCKR ISO-2022-JP ISO-2022-JP 39 RFC1468 ] (see…

…-ir-149 KS_C_5601-1989 KSC_5601 korean csKSC56011987 ISO-2022-KR ISO-2022-KR 37 RFC1557 ] (see also KS_C_5601-1987) RFC1557 ][ Woohyong_Choi csISO2022KR EUC-KR EUC-KR 38 RFC1557 ] (see also KS_C_5861-1992) RFC1557 ][ Woohyong_Choi csEUCKR ISO-2022-JP ISO-2022-JP 39 RFC1468 ] (see…

…l with a Korean charset (e.g., Hangul) encoded following the specification in [ RFC1557 ]. Since the charset parameter is provided, MIME and XML processors MUST treat the enclosed entity as encoded per RFC 1557 Since ISO-2022-KR has been defined to use only 7 bits of data, no con…

…rs must treat the enclosed entity as encoded per RFC 1557 . Since ISO-2022-KR [ RFC1557 ] has been defined to use only 7 bits of data, no content-transfer-encoding is necessary with any transport: for character sets needing 8 or more bits, considerations such as those discussed a…