01-18-2015
This looks to me like a UTF16 encoded file, except for the missing lead-in FF FE. While just removing the 00 chars may yield a valid file, especially when dealing with code points below 255, it may leave the file uninterpretable if high code points are in there. Use iconv to be on the safe side.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have two Solaris machines.
1. SunOS X 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-1500
2. SunOS Y 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-60
I am trying to buiild a project on both these machines. The Binary output file compiled on machine 2 runs on both the machines. Where... (0 Replies)
Discussion started by: scgupta
0 Replies
2. Filesystems, Disks and Memory
I just started using Terminal on my Mac this summer, and right now I am having problems making a shell script. This shell should run the "Microsoft Setup Assistant" once I run the Automator Script. Alas, I still have problems.
Here is the offending scriptlet:
Sudo Tcsh
root# cd... (2 Replies)
Discussion started by: chrisfrap
2 Replies
3. Solaris
I tried to decode a binary script using the command 'uudecode'. but it is giving error as 'No begining line'.
'uudecode -o <outfile name> <binary file>'
Please help me in resolving this. (4 Replies)
Discussion started by: vamshikrishnab
4 Replies
4. SCO
Hi
I am looking for sco xenix binary compatibility utility "cvtomf",(convert omf object to COFF object)
Would you please help me ?
tnx (3 Replies)
Discussion started by: javad1_maroofi
3 Replies
5. UNIX for Dummies Questions & Answers
I am using grep to match a pattern, but the output is strange.
$ grep -r -o "pattern" *
Gives me:
Binary file foo1 matches
Binary file foo2 matches
Binary file foo3 matches
To find the lines before/after, I then have to use the following on each file:
$ strings foo1 | grep -A1 -B1... (0 Replies)
Discussion started by: chipperuga
0 Replies
6. Shell Programming and Scripting
I am struck up with a problem and that is with output redirection.
I used all the ways for the redirection of the output of c binary to a file, still it is failing.
Here are the different ways which I have used:
./a.out | tee -a /root/tmp.txt 2>&1
./a.out | tee -a /root/tmp.txt 1>&1
./a.out |... (2 Replies)
Discussion started by: Maya29988
2 Replies
7. UNIX for Dummies Questions & Answers
Hello guys,
We had to move from a DC to another, and we are now facing an "issue" with some text files.
Looks like that some of our log files are set as binary:
file TuxConnectorURA.20121012
TuxConnectorURA.20121012: data or International Language text
less TuxConnectorURA.20121012... (2 Replies)
Discussion started by: EnioMarques
2 Replies
8. Shell Programming and Scripting
Hello *nix specialists,
Im working for a non profit organisation in Germany to transport DSL over WLAN to people in areas without no DSL. We are using Linksys WRT 54 router with DD-WRT firmware There are at the moment over 180 router running but we have to change some settings next time. So my... (7 Replies)
Discussion started by: digidax
7 Replies
9. Shell Programming and Scripting
Hello,
I want to parse another file, i just want the ascii content, here the result of command od -bc file
0000000 036 000 024 000 000 000 377 376 377 010 060 000 060 000 060 000
036 \0 024 \0 \0 \0 377 376 377 \b 0 \0 0 \0 0 \0
0000020 060 000 062 000 106 000... (21 Replies)
Discussion started by: protocomm
21 Replies
10. Web Development
Database Structure
Root Table
ID Root_ Node Level
1 A 0
2 B 1
3 C 1
Child Table
ID Left_Node Right_Node Root_Node Root_ID
1 B C A 1
... (1 Reply)
Discussion started by: Deepak Tiwari
1 Replies
LEARN ABOUT DEBIAN
punycode_encode
punycode_encode(3) libidn punycode_encode(3)
NAME
punycode_encode - API function
SYNOPSIS
#include <punycode.h>
int punycode_encode(size_t input_length, const punycode_uint [] input, const unsigned char [] case_flags, size_t * output_length, char []
output);
ARGUMENTS
size_t input_length
The number of code points in the input array and the number of flags in the case_flags array.
const punycode_uint [] input
An array of code points. They are presumed to be Unicode code points, but that is not strictly REQUIRED. The array contains
code points, not code units. UTF-16 uses code units D800 through DFFF to refer to code points 10000..10FFFF. The code points
D800..DFFF do not occur in any valid Unicode string. The code points that can occur in Unicode strings (0..D7FF and
E000..10FFFF) are also called Unicode scalar values.
const unsigned char [] case_flags
A NULL pointer or an array of boolean values parallel to the input array. Nonzero (true, flagged) suggests that the corre-
sponding Unicode character be forced to uppercase after being decoded (if possible), and zero (false, unflagged) suggests that
it be forced to lowercase (if possible). ASCII code points (0..7F) are encoded literally, except that ASCII letters are forced
to uppercase or lowercase according to the corresponding case flags. If case_flags is a NULL pointer then ASCII letters are
left as they are, and other code points are treated as unflagged.
size_t * output_length
The caller passes in the maximum number of ASCII code points that it can receive. On successful return it will contain the
number of ASCII code points actually output.
char [] output
An array of ASCII code points. It is *not* null-terminated; it will contain zeros if and only if the input contains zeros.
(Of course the caller can leave room for a terminator and add one if needed.)
DESCRIPTION
Converts a sequence of code points (presumed to be Unicode code points) to Punycode.
RETURN VALUE
The return value can be any of the Punycode_status values defined above except PUNYCODE_BAD_INPUT. If not PUNYCODE_SUCCESS, then out-
put_size and output might contain garbage.
REPORTING BUGS
Report bugs to <bug-libidn@gnu.org>. GNU Libidn home page: http://www.gnu.org/software/libidn/ General help using GNU software:
http://www.gnu.org/gethelp/
COPYRIGHT
Copyright (C) 2002-2012 Simon Josefsson.
Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.
SEE ALSO
The full documentation for libidn is maintained as a Texinfo manual. If the info and libidn programs are properly installed at your site,
the command
info libidn
should give you access to the complete manual.
libidn 1.25 punycode_encode(3)