Chinese character encodings

I wonder if someone here could tell me what’s the character encoding that is commonly used in China?
I received a link to some .zip-file when I asked some further info about a 433 MHz USB-dongle.
The problem is that the directory names and some file names contain weird characters – they seem to be displayed
as Latin1 characters, so google translate can’t make anything out of them.

One of the files is a .h-file that contains radio parameters, but I’m not sure which device they are for.
I wonder if the directory name could reveal it, but I can’t translate the directory name if I can’t convert the
weird characters of the name to Chinese characters.
The directory names look like this:
¼Ä´æÆ÷¼°ÅäÖÃÐÅÏ¢
Çý¶¯
Ïà¹ØÀý³Ì
´®¿Úµ÷ÊÔÈí¼þ

If you post a link to zip file we could check if we can extract correct names…

The original link that I got was
http://pan.baidu.com/s/1skw798L
But it was slow and had to restart downloading several times, so the following might work a bit better:
https://www.dropbox.com/s/rwl1msyjdhmw3 … 2.zip?dl=0

Oh, and I think, anyone interested can use it.

You might also make some headway from the website mentioned in one of the PDFs in that zip.
Try -> https://translate.google.co.uk/translat … rev=search
EDIT .. and here -> https://translate.google.co.uk/translat … rev=search

Downloaded Dropbox one and phone states it’s not unicode. But RAR – Android has all languages but chinese (has Thai, Jorean and Japanese!).

Also Sailfish gui gives me garbage.

It’s 23h here, tomorrow I’ll test on PC…

This might be closely related -> https://github.com/Seeed-Studio/RFBee/b … r/CCxCfg.h

There seems to be stuff for two (somewhat related) devices. The module with SPI interface and the dongle with USB/serial interface. Both using the CC1101-chip. The PDFs in the topmost directory I already translated with Google translate (not perfect, but good enough). The test might be sending stuff between the module and the dongle…

I started from the Fytoo-pages before asking from the seller…

What I’m interested in are the radio parameters used by the dongle. If the test code is for the module and for communicating with the dongle, then, it’s what I’m after – indirectly, but anyway. I have the CC1101 data sheets and I can check what the settings mean.

That ZIP-file is what I got when I asked for documentation of the dongle.

ahull wrote:This might be closely related -> https://github.com/Seeed-Studio/RFBee/b … r/CCxCfg.h

And this is not the first time I run into the character problem.

From the file 1100.c Linux uchardet says that it’s gb18030, but I still can’t get the comments to display right.
Opened with geany and set the encoding to that, but the characters are unchanged.

//*****************************************************************************************
//º¯ÊýÃû£ºSpisendByte(INT8U dat)
//ÊäÈ룺·¢Ë͵ÄÊý¾Ý
//Êä³ö£ºÎÞ
//¹¦ÄÜÃèÊö£ºSPI·¢ËÍÒ»¸ö×Ö½Ú
//*****************************************************************************************

I got the characters converted and the names translated by Google translate, but…

ls -R . > ../tree.txt
iconv -f GB18030 -t UTF-16 tree.txt > tree_conv.txt


I made a test but not able to analyze results (too much data):

It’s a brute force test run in Linux (or UNIX-like):

1) uncompress ZIP

2) Execute following BASH script:
#!/bin/bash

iconv -l |
sed 's|//$||' |
while read enc; do
printf "\n --- $enc ---\n\n"
find . | iconv -cf "$enc" 2>/dev/null
done


Example de one good candidate:

--- BIG-5 ---

.
./USB1100-232-穠+-穠<U+0080>.pdf
./RF1100-232-V2-outline.PCB
./簽穠+穠穠
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100_Opt.Bak
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.Opt
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.plg
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.M51
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.Uv2
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.LST
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.hex
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.OBJ
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100.c
./簽穠+穠穠/RF1100-232+畢佃縝++-+硰+鶪+-遲+/1100_Uv2.Bak
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_r.Uv2
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/LCD_12864s_driver.c
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/lcdcode.OBJ
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_s_Opt.Bak
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/NewMSG_stc51.plg
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/LCD_12864s_driver.LST
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/DS18B20.OBJ
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/DS18B20.h
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/lcdcode.LST
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_s_Uv2.Bak
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/main.LST
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_s.hex
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/main.c
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_s.Opt
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/DS18B20.c
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/LCD_12864s_driver.OBJ
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/STARTUP.LST
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_r.Opt
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/main.OBJ
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/DS18B20.LST
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/lcdcode.h
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_r_Opt.Bak
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/STARTUP.A51
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/1100.LST
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100.h
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/lcdcode.c
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_s.plg
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/IO_def.h
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/1100.OBJ
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/STARTUP.OBJ
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/1100.c
./簽穠+穠穠/RF1100_232+畢(托++厒SPI-+-遲+/RF1100_232C_test/cc1100_r_Uv2.Bak


Linux’s ‘uchardet’ could figure out the encoding (GB18030).
And I used ‘iconv’ to change the encoding.

The problem is now the translation. It looks like Google translate is not up to it and neither was Reverso.
Both produced nonsense.

Google translate:
麓庐驴脷碌梅脢脭脠铆录镁 -> Lu Lu donkey spoons of the United States and the United States

Reverso:
(the same) -> String on the new MUI error trying to log in rivets

turboscrew wrote: Lu Lu donkey spoons

Checking files I saw:

./脧脿鹿脴脌媒鲁脤/RF1100_232脌媒鲁脤(麓庐驴脷脫毛SPI脛拢驴茅脥篓脨脜拢漏/RF1100_232C_test:
Cc1100.h
Cc1100_s.hex
DS18B20.h
IO_def.h

There’s no other candidates for .h (or similar) files that are not for LCD so what you look for should be in one of these.

I’m not sure, but the most important for me now may be:
./录脛麓忙脝梅录掳脜盲脰脙脨脜脧垄/RF1101_232脨戮脝卢录脛麓忙脝梅脜盲脰脙.txt
(If only I knew what is this configuration for…)

i took ‘录脛麓忙脝梅录掳脜盲脰脙脨脜脧垄’ and for fun fed it to chrome and google

link is https://www.google.co.uk/search?q=%E5%B … e&ie=UTF-8

result page seems mainly about ugly cat, donkey and meat carrying on the back of various things. halogen, deer shed.
nothing stm32 related
srp

ahull wrote:turboscrew wrote: Lu Lu donkey spoons