I was wondering if it's feasible to have CP850 support in
future versions of Hotdoged.
I was wondering if it's feasible to have CP850 support in
future versions of Hotdoged.
I'll check this. I think it's possible if android supports this. There
is a lack of one-byte codepages support there, i.e. I had to write the conversion tables by myself for 866.
@CHRS: LATIN-1 2
I was wondering if it's feasible to have CP850 support in
future versions of Hotdoged.
I'll check this. I think it's possible if android supports this. There
is a lack of one-byte codepages support there, i.e. I had to write the
conversion tables by myself for 866.
Thank you! We use CP850 at our Brazilian Portuguese echos here
at Fidonet and CP850 support would be greatly appreciated.
Thank you! We use CP850 at our Brazilian Portuguese echos here
at Fidonet and CP850 support would be greatly appreciated.
we should not care of incomming maps, but support outgoing maps to use supported charsets known in ALL fidonet tossers, LATIN-1 is well
supported even on amiga, starting do unicode or unsupported charsets
make it worse
but all kinds of incomming maps is valid, if it does not mangle what charsets it writed in
last but not least here, you did not use 8bit anywhere :)
wish to hotdoged, use charset dynamic based on content is 7bit or not
I understand, but the problem is not with me specifically.
The Brazilian Portuguese echos of Fido (BR.*) use CP850
especifically by design and by some old software thatīs still in use, hence everyone write there using CP850, even myself (I change my CHRS
for the BR.* echos)
In that case, it would be awesome to have CP850 support for
HOTDOGED.
last but not least here, you did not use 8bit anywhere :)
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 995 |
Nodes: | 10 (0 / 10) |
Uptime: | 198:33:00 |
Calls: | 13,022 |
Files: | 186,574 |
Messages: | 3,284,717 |