A quick peek at sample.conf shows that the first byte in the lines is a null byte. It's a safe bet that what you are seeing is a sideeffect of c string functions interpreting a null byte as end of string.
For experimentation's sake, does the discrepancy persist if you substitute a 001 byte for the 000 bytes?
If it does not, mystery solved. If it does, weird. Could that sed implementation be filtering out control characters?
I posted this in Shell scripting... maybe I'll try it in this forum..
*****************
I wrote a script to stop a process,truncate its log files and re-start the process...
We are using Progress Software in Unix ( Sun Sparc)
When ever I start this progress program , it should kick off a... (1 Reply)
Hi,
I wrote a script to stop a process,truncate its log files and re-start the process...
We are using Progress Software in Unix ( Sun Sparc)
When ever I start this progress program , it should kick off a C pgm in the background..
The script work perfectly fine when I run it from command... (4 Replies)
All,
I have a script that runs on 2 servers and there seems to be something wrong. It's producing different results on the 2 servers.
Here is the script on server1 which is behaving correctly but on 2 behaving differently.
2nd server:
I couldn't make out whats the error is?... (5 Replies)
Guys i have strange behaviour with command output being saved in a variable instead of a tmp file.
1. I suck command output into a variable
Sample command output
# cleanstats
DRIVE INFO:
----------
Drv Type Mount Time Frequency Last Cleaned Comment
*** ****... (1 Reply)
Here is my test script:
#!/bin/sh
result=`jobs`
echo "
Jobs:
"$result
result=`ls`
echo "
LS
"$result
Here is the output:
Jobs:
LS
0 1 2 3 4 5 6 7 gcd initialize.sh #inter_round_clean.sh# inter_round_clean.sh inter_round_clean.sh~ look parallel_first_run.sh... (3 Replies)
Hi,
We have few hundered scripts using cut command in thousands of lines. On HP-UX shell script developer used echo "ABCEFG" | cut -c -1-3 to cut first three character of the string. We recently moved to Linux and this command throws error. I think this might be due to different version of... (3 Replies)
HI all
I have written a ksh to execute PL/sql procedure and generate the log file. The script is working fine to the extent of calling the taking input, executing PL/SQL procedure.
On one server the log file is getting generated properly. i,e it shows the DBMS output . The log file size was... (9 Replies)
Hi, all.
Here's the problem:
sed '/FOO/,/BAR/p'
That should print anything between FOO and BAR, right?
Well, let's say I have file.txt that contains just one line "how are you today?".
Then I run something like the above and get:
$ sed '/how/,/today/p' file.txt
how are you... (9 Replies)
I have a memory card of my Nokia N73 attached to laptop. There are a few partitions.
Why all partitions behave differently? As clear from the attachments, for some partition, delete option is disabled. See 'Disk 1' which is my memory card.
Here, patition 'G' (CHECK), i created in windows. The... (6 Replies)
Hi I'm having a problem with a sed command that I thought I was using correctly but apparently that's not the case.
I was hoping someone here could point out what it is I am doing wrong?
I am using the print, no print option for a matched pattern in sed. Everything seemed to be working fine... (5 Replies)
Discussion started by: Paul Walker
5 Replies
LEARN ABOUT FREEBSD
gb18030
GB18030(5) BSD File Formats Manual GB18030(5)NAME
gb18030 -- GB 18030 encoding method for Chinese text
SYNOPSIS
ENCODING "GB18030"
DESCRIPTION
The GB18030 encoding implements GB 18030-2000, a PRC national standard for the encoding of Chinese characters. It is a superset of the older
GB 2312-1980 and GBK encodings, and incorporates Unicode's Unihan Extension A completely. It also provides code space for all Unicode 3.0
code points.
Multibyte characters in the GB18030 encoding can be one byte, two bytes, or four bytes long. There are a total of over 1.5 million code
positions.
GB 11383-1981 (ASCII) characters are represented by single bytes in the range 0x00 to 0x7F.
Chinese characters are represented as either two bytes or four bytes. Characters that are represented by two bytes begin with a byte in the
range 0x81-0xFE and end with a byte either in the range 0x40-0x7E or 0x80-0xFE.
Characters that are represented by four bytes begin with a byte in the range 0x81-0xFE, have a second byte in the range 0x30-0x39, a third
byte in the range 0x81-0xFE and a fourth byte in the range 0x30-0x39.
SEE ALSO euc(5), gb2312(5), gbk(5), utf8(5)
Chinese National Standard GB 18030-2000: Information Technology -- Chinese ideograms coded character set for information interchange --
Extension for the basic set, March 2000.
The Unicode Standard, Version 3.0, The Unicode Consortium, 2000.
STANDARDS
The GB18030 encoding is believed to be compatible with GB 18030-2000.
BSD August 10, 2003 BSD