Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Change encoding, no removing special chars. inconv Post 303011178 by Don Cragun on Sunday 14th of January 2018 04:12:44 PM
Old 01-14-2018
You need to figure out whether the file you are trying to convert from is encoded in ISO 8859-1, ISO 8859-15, Windows 1252, or some other codeset. All three of the ones listed here have the lower 128 characters with the same encodings as US ASCII and all of them contain the í and ó characters, but I'm not sure if they are encoded the same way in the three listed codesets. The only way iconv can work correctly is if you correctly tell it in what codeset the file it is reading is encoded and tell it to what codeset you want the output file to be written.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Supress special chars in vi

Hi, One of our application is producing log files. But if we open the log file in vi or less or view mode, it shows all the special characters in it. The 'cat' shows correctly but it shows only last page. If I do 'cat' <file_name> | more, then again it shows special characters. ... (1 Reply)
Discussion started by: divakarp
1 Replies

2. Shell Programming and Scripting

treating special chars

Hi, I need some advise on treating non printable chars over ascii value 126 Case 1 : On some fields in the text , I need to retiain then 'as-is' and load to a database.I understand it also depends on database codepage. but i just wanna know how do i ensure it do not change while loading... (1 Reply)
Discussion started by: braindrain
1 Replies

3. Shell Programming and Scripting

special chars arrangement in code

here is my simple script to show process and owners except me: ps `-ef |grep xterm |grep -v aucar` | while read a1 a2 a3 a4 a5 a6 a7 a8 do echo KILL..\($a1\).. $a2 |more done how can I pass values from command "ps -ef |grep xterm|grep -v aucar" to ? because above command... (2 Replies)
Discussion started by: xramm
2 Replies

4. UNIX for Dummies Questions & Answers

Strings with Special chars in IF condition

I was trying to run a code to check if a fax number is empty or not. for that, I've written the following code which is throwing an error. #!/bin/ksh fax= "999-999-9999" if ; then fax_no="000-000-0000" else fax_no=$fax fi echo $fax_no And I get the... (7 Replies)
Discussion started by: hooaamai
7 Replies

5. Shell Programming and Scripting

print all between patterns with special chars

Hi, I'm having trouble with awk print all characters between 2 patterns. I tried more then one solution found on this forum but with no success. Probably my mistakes are due to the special characters "" and "]"in the search patterns. Well, have a log file like this: logfile.txt ... (3 Replies)
Discussion started by: ginolatino
3 Replies

6. Shell Programming and Scripting

All strings within two special chars

I have a file with multiple lines. From each line I want to get all strings that starts with '+' and ends with '/'. Then I want the strings to be separated by ' + ' Example input: +$A$/NOUN+At/NSUFF_FEM_PL+K/CASE_INDEF_ACC Sample output: $A$ + At + K (20 Replies)
Discussion started by: Viernes
20 Replies

7. UNIX for Dummies Questions & Answers

How to search for a string with special chars?

Hi guys, I am trying to find the following string in a file, but I always get pattern not found error, not sure what is missing here. Can you help please? I do a less to open the xrates.log and then do a /'="18"' in the file and tried various combinations to search the below string. String... (8 Replies)
Discussion started by: santokal
8 Replies

8. UNIX for Advanced & Expert Users

Removing special chars from file and maintain field separator

Running SunOs 5.6. Solaris. I've been able to remove all special characters from a fixed length file which appear in the first column but as a result all subsequent columns have shifted to the left by the amount of characters deleted. It is a space separated file. Line 1 in input file is... (6 Replies)
Discussion started by: iffy290
6 Replies

9. Solaris

View file encoding then change encoding.

Hi all!! I´m using command file -i myfile.xml to validate XML file encoding, but it is just saying regular file . I´m expecting / looking an output as UTF8 or ANSI / ASCII Is there command to display the files encoding? Thank you! (2 Replies)
Discussion started by: mrreds
2 Replies

10. UNIX for Beginners Questions & Answers

Shell script to split data with a delimiter having chars and special chars

Hi Team, I have a file a1.txt with data as follows. dfjakjf...asdfkasj</EnableQuotedIDs><SQL><SelectStatement modified='1' type='string'><! The delimiter string: <SelectStatement modified='1' type='string'><! dlm="<SelectStatement modified='1' type='string'><! The above command is... (7 Replies)
Discussion started by: kmanivan82
7 Replies
iconv(1)							   User Commands							  iconv(1)

NAME
iconv - code set conversion utility SYNOPSIS
iconv [-cs] -f frommap -t tomap [file]... iconv -f fromcode [-cs] [-t tocode] [file]... iconv -t tocode [-cs] [-f fromcode] [file]... iconv -l DESCRIPTION
The iconv utility converts the characters or sequences of characters in file from one code set to another and writes the results to stan- dard output. If no conversion exists for a particular character, an implementation-defined conversion is performed on this character. The list of supported conversions and the locations of the associated conversion tables are provided in the iconv(5) manual page. OPTIONS
The following options are supported: -c Omits any characters that are invalid in the codeset of the input file from the output. When -c is not used, the results of encountering invalid characters in the input stream depend on the specified codesets for the conversion. Invalid char- acters can be either those that are not valid characters in the codeset of the input file or those that have no corre- sponding character in the codeset of the output file. The presence or absence of -c does not affect the exit status of iconv. When fromcode is specified for the fromcodeset of the -f option or tocode is specified for the tocodeset of the -t option, the specification of -c may be ignored. -f fromcodeset Identifies the code set of the input file. The following two forms of the fromcodeset option-argument are recognized: fromcode The fromcode option-argument must not contain a slash (/) character. It is interpreted as the name of one of the codeset descriptions. frommap The frommap option-argument must contain a slash character. It is interpreted as the pathname of a charmap file as defined in charmap(5). If the pathname does not represent a valid, readable charmap file, the results are undefined. If this option is omitted, the codeset of the current locale is used. -l Writes all supported fromcode and tocode values to standard output. -s Suppresses any messages written to standard error concerning invalid characters. When -s is not used, the results of encountering invalid characters in the input stream depend on the specified codesets for the conversion. Invalid charac- ters can be either those that are not valid characters in the codeset of the input file or those that have no correspond- ing character in the codeset of the output file. The presence or absence of -s does not affect the exit status of iconv. When fromcode is specified for the fromcodeset of the -f option or tocode is specified for the tocodeset of the -t option, the specification of -s may be ignored. -t tocodeset Identifies the code set used for the output file. The following two forms of the tocodeset option-argument are recog- nized: tocode The tocode option-argument must not contain a slash (/) character. It is interpreted as the name of one of the codeset descriptions. tomap The tomap option-argument must contain a slash character. It is interpreted as the pathname of a charmap file as defined in charmap(5). If the pathname does not represent a valid, readable charmap file, the results are undefined. If this option is omitted, the codeset of the current locale is used. If either -f or -t represents a charmap file but the other does not, or is omitted, or if both -f and -t are omitted, iconv fails as an error. OPERANDS
The following operands are supported: file A path name of an input file. If no file operands are specified, or if a file operand is '-', the standard input is used. EXAMPLES
Example 1 Converting and storing files The following example converts the contents of file mail1 from code set 8859 to 646fr and stores the results in file mail.local: example% iconv -f 8859 -t 646fr mail1 > mail.local ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of iconv: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. FILES
/usr/lib/iconv/iconv_data list of conversions supported by conversion tables ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
iconv(3C), iconv_open(3C), attributes(5), charmap(5), environ(5), iconv(5), iconv_unicode(5), standards(5) NOTES
Make sure that both charmap files use the same symbolic names for characters the two codesets have in common. The output format of the -l option is unspecified. The -l option is not intended for shell script usage. When fromcode or tocode is specified for the codeset conversion, iconv uses the iconv_open(3C) function. If iconv_open(3C) fails to open the specified codeset conversion, iconv searches for an appropriate conversion table. As for the supported codeset conversion by iconv_open(3C), please refer to iconv(5) and iconv_locale(5). SunOS 5.11 14 Nov 2003 iconv(1)
All times are GMT -4. The time now is 11:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy