What must be done: 1) add CP895 into iconv and 2) get Golded+
working with 1byte against UTF and back conversion
No one will ever add this encoding to iconv or the Windows
distribution: itīs used too rarely. Reversible encoding should work,
so this encoding can be used with a conversion table.
That will be a waste of time and energy. Just skip that fase and go directly to UTF-8. That is the future for Fidonet. For the rest of the digital world UTF-8 already is the present.
What must be done: 1) add CP895 into iconv and 2) get Golded+
working with 1byte against UTF and back conversion
No one will ever add this encoding to iconv or the Windows
distribution: itīs used too rarely. Reversible encoding should
work, so this encoding can be used with a conversion table.
Somebody told me "never say never" ;-) In use of linux - why I could
not add module in gconv by myself? Not sure about Windows nor OS/2.
Again, thank you for your work.
That will be a waste of time and energy. Just skip that fase and
go directly to UTF-8. That is the future for Fidonet. For the
rest of the digital world UTF-8 already is the present.
You are (as usual) right.
Majority in r42 agreed to wait a bit longer. But that is OK.
What's there to wait for? All you need to do in R42 is accept a
document that clearly states that the primary encoding used is UTF-8.
| Sysop: | Daphantom |
|---|---|
| Location: | Washington, IL. |
| Users: | 3 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 145:52:59 |
| Calls: | 28 |
| Calls today: | 1 |
| Files: | 21,932 |
| D/L today: |
136 files (12,515K bytes) |
| Messages: | 28,163 |