"List" decoding problem And TCMD crash.

Aug 3, 2010
5
0
#1
Sorry, my English is very very poor.

I purchased and upgrade from 4NT v6 to TCMD V11 last two days.

OS: Windows 7 x64 Trad Chinese.

4NT v6 work on it very well.

Now I got two problems:

1.Both 32/64-bit TCMD.exe can not be use - everytime I run it, it just show "conhost.exe crash", and close itself.
By the way ,this is not really important.

2.The LIST command from TCC can not decoding Chinese word correctly. This is very big trouble.
It can normally decoding ENGLISH from ISO-8859-1 and UTF-16.
It can normally decoding Chinese from UTF-16.
It cannot decoding Chinese Big5 from BIG-5. Only English show on screen.

Althrough the LIST commnd from 4NT v6 never show UTF-16 correct, it does show Chinese Big5 very well.

So, may JPSoftware fix the problem? or just enhance LIST command to show all other encodings available in Windows just like EMEDITOR?

Thanks very much.
==
 

rconn

Administrator
Staff member
May 14, 2008
10,746
97
#2
> 1.Both 32/64-bit TCMD.exe can not be use - everytime I run it, it just
> show "conhost.exe crash", and close itself.
> By the way ,this is not really important.
Conhost.exe is a Microsoft program (which runs console apps in Win 7).
You'll need to contact Microsoft support for help with conhost.


> 2.The LIST command from TCC can not decoding Chinese word correctly.
> This is very big trouble.
> It can normally decoding ENGLISH from ISO-8859-1 and UTF-16.
> It can normally decoding Chinese from UTF-16.
> It cannot decoding Chinese Big5 from BIG-5. Only English show on
> screen.
Take Command and TCC only support Unicode (UTF-16). We have no expertise
with BIG-5, or any way to develop or test that encoding.

Rex Conn
JP Software
 
Aug 3, 2010
5
0
#3
Sorry, my English is very very poor.

Conhost.exe is a Microsoft program (which runs console apps in Win 7).
You'll need to contact Microsoft support for help with conhost.
So you mean that micro$oft do something bad to your main product.

I don't know why 4NT v6 do not crash conhost, and TCMD v11 do crash conhost.
Take Command and TCC only support Unicode (UTF-16). We have no expertise
with BIG-5, or any way to develop or test that encoding.
Rex Conn
JP Software
Ok, UTF-16 only.

I must remind you that "Type" command could show Chinese Big5 very well.

If TCMD really "only" support UTF-16 just like you said, please tell me why all those ASCII-encoding BATCH File could work normally? or you want told me that "TCMD now support utf-8 English part very well, it's a magic revolution!"

Isn't it?
 

rconn

Administrator
Staff member
May 14, 2008
10,746
97
#4
> ---Quote (Originally by rconn)---
> Conhost.exe is a Microsoft program (which runs console apps in Win 7).
> You'll need to contact Microsoft support for help with conhost.
> ---End Quote---
> So you mean that micro$oft do something bad to your main product.
>
> I don't know why 4NT v6 do not crash conhost, and TCMD v11 do crash
> conhost.
TCMD doesn't have anything to do with conhost.

Conhost.exe is the (Microsoft) program that runs console apps (like TCC).
TCMD asks Windows to start a console app (like TCC), and Windows starts
conhost -- which is then supposed to run tcc.exe, but on your system it
crashes instead. There's nothing JP Software can do about that; it's a
Windows bug and only Microsoft can fix it.

We've had one other report of conhost failing on a Win 7 Chinese Windows (no
reports of problems with any other language).


> ---Quote (Originally by rconn)---
> Take Command and TCC only support Unicode (UTF-16). We have no
> expertise with BIG-5, or any way to develop or test that encoding.
> ---End Quote---
> Ok, UTF-16 only.
>
> I must remind you that "Type" command could show Chinese Big5 very
> well.
TYPE just dumps the file contents to STDOUT.


> If TCMD really "only" support UTF-16 just like you said, please tell
> me why all those ASCII-encoding BATCH File could work normally? or you
> want told me that "TCMD now support utf-8 English part very well, it's
> a magic revolution!"
The LIST question was about character encodings within TCC (not TCMD), not
file encoding. TCC supports either ASCII or Unicode (UTF-16) files for all
of its internal commands (and batch processing). It does not support BIG-5.

Rex Conn
JP Software
 
Aug 3, 2010
5
0
#5
Soeey, my English is very very poor.

TCMD doesn't have anything to do with conhost.
Fine, I don't use TCMD GUI. So TCMD crash is not big problem.

TYPE just dumps the file contents to STDOUT.
The LIST question was about character encodings within TCC (not TCMD), not
file encoding. TCC supports either ASCII or Unicode (UTF-16) files for all
of its internal commands (and batch processing). It does not support BIG-5.
There is one thing very clear:

All products from JPSoftware NEVER supoort BIG-5.

So, why 4NT v6 could LIST a BIG-5 text file very well and TCC V11 could not?

The FACT is that you just proceed BIG-5 as ASCII, Chinese version windows will identify which is Chinese WORD and which is not and display it correctly. That is the reason 4NT v6 DO LIST Chinese BIG-5 TEXT very well.

I think the problem is that TCC v11 (or more early version?) update LIST source code to handle both ASCII & UTF-16 word. And those new proceed method would make ASCII be changed permanently (inside memory, not file) or they used an different windows API to display those word, so those Chinese Word could not be identify by Chinese Windows anymore.
 
Aug 3, 2010
5
0
#6
Sorry, my English is very very poor.

I tried 4NT v8 and I found that LIST is the same with TCC v11.

So, I suddenly figure out that the problem is "unicode version".

I will keep a copy 4NT v6 ASCII version to serve those ASCII file.

Thanks for respond above.