, 祭 筮 宩 ࠢ
襩. ᥣ ᥬ줥 , ᥬ
⭠ ⭠ , १ , . . ... 㯠... ... ࠧ... ⮢ 墠뢠饣
...
Looks like it works much better than 'trans' -width modifier.
This time I only used 'trans' to translate unbounded English text and
then 'fold' and 'sed' to format the Russian text shown below. 'iconv' was then deployed to convert utf8 Russian text to cp866. Looks like it works much better than 'trans' -width modifier.
Боюсь, наша жизнь должна показаться очень скучной и тихой по сравнению
с вашей. Мы всего лишь восемьдесят молодых блондинок, всем от
шестнадцати до девятнадцати с половиной лет, отрезанные от мира в своем
замке, и никто не может нас защитить. Оооо. Это одинокая жизнь...
купание... одевание... раздевание... изготовление захватывающего
нижнего белья...
That's neat-o.
Keep up the good fight! :)
I note that you convert them back to utf-8 before replying. I do the same here except that after replying I convert them back to the
supported 8-bit character set, cp866 in this case. To be honest utf-8 for all would be best especially when given bogus information in
so-called ftn standards. Simply shocking methinks.
For sure. Someone has to be on the side of what is right and proper. :-)
I believe this client forces utf-8 when posting, which is fine.
I do have other clients for testing purposes that can send it back
in CP866, but why?
Be prepared to be in the fight for the long haul. :)
@MSGID: 1:154/10 65f5a090
@REPLY: 1:153/7001.2989 65f5448c
@PID: smapinntpd/linux 2.1.9
@CHRS: UTF-8 4
@TZUTC: -0500
@TID: hpt/lnx 1.9 2024-02-05
On Sat, 16 Mar 2024 07:04:44 GMT, Maurice Kinal -> Zoot wrote:
This time I only used 'trans' to translate unbounded English text and
then 'fold' and 'sed' to format the Russian text shown below.?? 'iconv'
was then deployed to convert utf8 Russian text to cp866.?? Looks like it
works much better than 'trans' -width modifier.
???????, ???? ??????? ????????? ???????????
?????? ????????? ?? ???????? ??? ?????????? ?
??????. ??? ??????? ????? ????????????? ??????????
?????????????, ???? ??? ????????????? ????
??????????????? ? ?????????????? ???,
??????????? ??? ????? ? ?????? ?????, ?? ???????
?? ??????? ??? ??????????. ????????. ????? ????????????
???????... ????????... ???????????...
????????????... ?????????????????
???????????????? ??????????? ?????...
That's neat-o. Keep up the good fight! :)
Regards,
Nick
... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10) SEEN-BY: 103/705 120/616 123/10 124/5016 153/757 7001 154/10 30 40 50 700 SEEN-BY: 203/0 220/90 221/0 1 6 360 226/18 70 240/1120 5832 280/464 5003 SEEN-BY: 292/8125 301/1 310/31 320/219 341/66 234 396/45 423/81 460/58 467/888 SEEN-BY: 633/280 712/848 770/1 2320/105 3634/12 5020/400 @PATH: 154/10 280/464 221/1
@MSGID: 1:153/7001.2989 65f5448c
@CHRS: CP866 2
Hey Zoot!
This time I only used 'trans' to translate unbounded English text and then 'fold' and 'sed' to format the Russian text shown below. 'iconv' was then deployed to convert utf8 Russian text to cp866. Looks like it works much better than 'trans' -width modifier.
?????, ???? ????? ?????? ?????????? ????? ??????? ? ????? ?? ?????????
? ?????. ?? ????? ???? ??????????? ??????? ?????????, ???? ??
??????????? ?? ???????????? ? ????????? ???, ?????????? ?? ???? ? ?????
?????, ? ????? ?? ????? ??? ????????. ????. ??? ???????? ?????...
???????... ????????... ??????????... ???????????? ??????????????
??????? ?????...
Life is good,
Maurice
-o o- o- -o o- -o o- o- -o o- o- o- o- o- -o -o (\ /) /) (\ /) (\ /) /) (\ /) /) /) /) /)
(\ (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
^^ ^^ ^^ ... Fidonet 4K - Sweet Sixteen Penguins of the Apocalypse. --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)
SEEN-BY: 103/705 124/5016 134/100 153/135 143 148 757 802 7001 154/10 30 203/0 SEEN-BY: 221/0 1 6 360 240/1120 5832 280/464 5003 292/8125 301/1 310/31 SEEN-BY: 320/219 341/66 234 396/45 423/81 460/58 467/888 633/280 712/848 770/1 SEEN-BY: 3634/12 5020/400
@PATH: 153/7001 757 280/464 221/1
Did not go over well with Aftershock.
HTTPS://ibb.co/rx9V6kx
This one was perfectly readable in Aftershock, but the reply does not cooperate.
This time I only used 'trans' to translate unbounded English text and
then 'fold' and 'sed' to format the Russian text shown below. 'iconv'
was then deployed to convert utf8 Russian text to cp866. Looks like it works much better than 'trans' -width modifier.
, 祭 筮 宩 ࠢ
襩. ᥣ ᥬ줥 , ᥬ
⭠ ⭠ , १
, . . ...
㯠... ... ࠧ... ⮢ 墠뢠饣
...
Did not go over well with Aftershock.^^^^^
HTTPS://ibb.co/rx9V6kx
This one was perfectly readable in Aftershock, but the reply does
not cooperate.
Let's see how this one gets back to you. ;)
Did not go over well with Aftershock.^^^^^
HTTPS://ibb.co/rx9V6kx
Please use lowercase, so my terminal recognises it as an url and shows
it as a clickable link! ;-)
Did not go over well with Aftershock.
HTTPS://ibb.co/rx9V6kx
From the looks of that screenshot, it doesn't look like it
quotes very well, either, going from 80 or more characters
wide to 50 characters. But I would imagine if there were
no initials before the quoted text, it would probably work
better.
Either way, that's because you seem to have Aftershock
setup for CP437 charset. Those kind of UTF-8 characters do
not translate to CP437, at all.
Did Maurice's original message show up ok for you? Because
I don't think CP866 (at least those characters) translates
to CP437, either.
Can Aftershock use different charsets?
HTTPS://ibb.co/rx9V6kx
From the looks of that screenshot, it doesn't look like it
quotes very well, either, going from 80 or more characters
wide to 50 characters. But I would imagine if there were
no initials before the quoted text, it would probably work
better.
It's not so bad. The message can also be viewed in landscape.
Not surprising given that CP437 doesn't support CP866
encoding. The only encoding that properly supports
differing languages is utf8. CP437 falls short of
supporting anything other than the so-call higher ascii,
which of course is bogus. All ascii are 7-bit characters
and is well supported by most encodings in the range of
0x00 to 0x7f. Anything above that isn't ascii, higher or
otherwise.
So.. you're implying that utf8 should be baked into fidonet?
A vast majority of retro systems and software would still be
limited to the 7-bit chars and high-ascii,
so.. what's the urgency for utf8?
So.. you're implying that utf8 should be baked into fidonet?
It already is. Has been for over a decade now.
so.. what's the urgency for utf8?
No urgency other than being first and best, which
undoubtably I am ... or at least I used to be. I had it
working before it became part of fts-5003.001.
What I meant was should it be "the" standard in character support
in fidonet products?
There is nothing stopping anyone setting up an exclusive/pure
utf8-based ftn-based network.
you *had* to have it working before it became part of
fts-5003.001. :D
What I meant was should it be "the" standard in character support
in fidonet products?
No but it definetly should be if one wishes to claim a completely capable product. I would wish no less for you and yours.
... 私の墓石は DejaVu Sans Mono で刻まれます
it feels kind of lame that BBS systems still use codepages.
it displays all the line drawing and pseudo graphic characters
(imo) better than almost all the retro fonts ever did..
IRC was going to be UTF-8 and if you couldn't read what was
written too bad.
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 19:29:22 |
| Calls: | 516 |
| Files: | 7,032 |
| Messages: | 288,164 |