REPLY: 1:104/117 654854ca   
   MSGID: 1:154/10 65496a63   
   CHRS: UTF-8 2   
   TZUTC: -0600   
   TID: hpt/lnx 1.9 2023-02-24   
   Hello Vitaliy,   
      
   On Sunday November 05 2023 19:31, you wrote to me:   
      
    VA> Привет, Nicholas!   
      
    VA> 05 Nov 23 19:03, ты писал(а) мне:   
      
   I may not be able to read some of the above, but it sure looks nice! ;)   
      
    VA> My plan is to enhance conversion code which uses iconv in linux   
    VA> builds. And then you won't need any translation tables for charsets   
    VA> known by iconv. It will take some time, because changes are not so   
    VA> small.   
      
   Would you suggest going back to the b20231028 code then until you're done   
   messing around with it?   
      
    VA>>> Just in case - you understand, that GoldEd can't properly work   
    VA>>> with UTF-8 local charset if any international character used?   
      
    NB>> Do you have any examples?   
      
    VA> GoldEd charset translation code can translate one byte encodings to   
    VA> multibyte, but not the opposite.   
      
    VA> So if you write your message in CP437 and export it to UTF-8 - it will   
    VA> work fine if such translation table exists. Now imagine that your   
    VA> local charset is CP437 and message is in UTF-8. That won't work   
    VA> because translation tables size is only 256 bytes and UTF-8 code may   
    VA> have up to 6 bytes per code point.   
      
   Ah yes. Understood. My local charset is UTF-8. Sometimes I try to do   
   translations of incoming messages, but that's about it.   
      
    VA> External editor solves some issues, but not all. Would be cool to have   
    VA> UTF-8 used for internal string representation, but that's huge work.   
      
   It solves most, at least for Fidonet messaging. Most messages are US-ASCII,   
   CP437/850, CP866, or UTF-8, which I can handle here just fine.   
      
    VA> What is your XLatLocalSet, XLatImport, XLatExport?   
      
   All are currently set to UTF-8. However, sometimes I like to test XLatImport   
   CP437. It helps on some messages, but since my locale is completely UTF-8 it   
   isn't perfect, usually when related to ANSI escape sequences.   
      
   Regards,   
   Nick   
      
   ... "Take my advice, I don't use it anyway."   
   --- GoldED+/LNX 1.1.5-b20231030   
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 1/19 123 15/0 16/0 18/200 19/37 90/1 103/705 105/81 106/201   
   SEEN-BY: 120/616 123/10 130 131 124/5016 129/305 142/104 153/757 7715   
   SEEN-BY: 154/10 30 40 50 700 203/0 218/700 220/90 221/0 6 226/18 30   
   SEEN-BY: 227/114 229/110 112 113 206 307 317 400 426 428 452 470 664   
   SEEN-BY: 229/700 240/77 1120 2100 5411 5413 5824 5832 5853 6309 266/512   
   SEEN-BY: 280/464 5003 5555 282/1038 291/111 292/854 8125 301/1 305/3   
   SEEN-BY: 310/31 317/3 320/119 219 319 2119 322/0 757 326/101 341/66   
   SEEN-BY: 341/234 342/200 396/45 423/120 460/58 633/280 712/848 770/1   
   SEEN-BY: 2320/105 2432/390 2454/119 3634/12 5020/400   
   PATH: 154/10 280/464 240/5832 320/219 229/426