[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: package description : cocot



Yukiharu Yabuki wrote:
> Justin B Rye <jbr@edlug.org.uk> wrote:
>> It sounds as if the idea is that you'd run "cocot ssh example.org",
>> and it would act as a wrapper translating the output of remote
>> commands into your local iso-2022-jp.  Let me know if I'm getting it
>> wrong...
>
> Exactly, you are right. see also below Ascii Art Picture.    
[...]
>> It would be helpful if you would describe that scenario in more
>> detail.  If I'm using en_US.iso88591 locally and en_US.utf8 on the
>> remote host, what will cocot show in place of symbols like “€”?
>> 
>> What goes wrong if the remote locale isn't "the same language"?
>
> Japanese has 4 character encoding.
> There are Shift-JIS(Mirosoft friendly),
> EUC-JP, UTF8 and ISO-2022-JP(a.k.a JIS). In recently debian system
> uses UTF8. but some survivied legacy debian system still use EUC-JP.

You mentioned that cocot uses CP932 as its default for the terminal
and expects the other encoding involved to be EUC-JP.  I hope it
checks instead of assuming it should default to a Japanese legacy
encoding on my en_GB.utf8 system!  That would be a bug, or at least
something that should be clearly signposted in documentation.

> Terminal(putty) ---- Machine A(EUC-JP) -+--- Machine 01(EUC-JP)
>                      ssh(gate keeper)   |
>                                         +--- Machine 02(SJIS)
>                                         |
>                                         +--- Machine 03(UTF8)
>                                         |
>                                         +--- Machine 04(ISO-2022-JP)

This seems to imply that the terminal I'm starting from is on a
Windows box.  But unless you can install .debs under Cygwin, that
can't be the function of this package.  You must mean that cocot is 
installed on A, and I'm running "cocot ssh machine01.localnet" to
connect onwards through the gateway server.  Is that right?

Are there less esoteric uses for cocot on Debian?  Perhaps I might
use it to connect from machine04.localnet to machine02.localnet?  Or
use it on a single machine where the system logs are in a different
encoding from my desktop environment ("cocot tail -f syslog")?

If it's really only useful on a SSH-stepping-stone server, and if
its options all assume that the language involved is Japanese, the
description needs to be much more specific.
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package


Reply to: