Sponsored Content
Top Forums Shell Programming and Scripting Cygwin vi XML file encoding problem Post 302440322 by fpmurphy on Tuesday 27th of July 2010 01:13:16 AM
Old 07-27-2010
UTF-16 is a valid XML encoding for a document. Line terminators between elements are not part of the XML standard per se. So long as the document is well-formed, it is valid.

I suspect that what you want to do is to convert the document into a more viewable format i.e. UTF-8 If this is the case, have a look at the iconv man page.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Problem printing the property of xml file via shell script

Hi, I have a config.xml which cointains the tags like <CONFIG> <PROPERTY name="port" value="1111"/> <PROPERTY name="dbname" value="ABCDE"/> <PROPERTY name="connectstring" value="xyz/pwd"/> </CONFIG> This file is in some directory at UNix box. I need to write a... (4 Replies)
Discussion started by: neeto
4 Replies

2. AIX

get the file encoding

Hello! The system is AIX 5.3 Give please command or script to get the file encoding (1 Reply)
Discussion started by: vinment
1 Replies

3. Shell Programming and Scripting

How to find the file encoding and updating the file encoding?

Hi, I am beginner to Unix. My requirement is to validate the encoding used in the incoming file(csv,txt).If it is encoded with UTF-8 format,then the file should remain as such otherwise i need to chnage the encoding to UTF-8. Please advice me how to proceed on this. (7 Replies)
Discussion started by: cnraja
7 Replies

4. Solaris

Encoding problem

Hi All, Hope you can help me with the below :). I'm working on a script on SUN solaris and I'm facing a problem with the number encoding as shown below, 1 is encoded to 31 (this is ASCII so it's ok) 11 is encoded as B118 !!! don't know why 111 is encoded as B1580C !!! don't know why ... (4 Replies)
Discussion started by: /dev/bag
4 Replies

5. Shell Programming and Scripting

How to achieve UTF-8 encoding & URL escape in an xml file?

Is there any i can achieve entity escaping, URL escaping & UTF-8 encoded for the xml generated through shell script? #! /bin/bash echo "<path>" >> file.xml for x in `ls filename*` do echo -e "\t<dir>" >> file.xml echo -e "\t\t<file>$x</file>" >> file.xml... (0 Replies)
Discussion started by: vel4ever
0 Replies

6. Programming

problem with accessing online XML file

Hi everyone, I am trying to access an online XML file, for example: <a href="http://www.rgraph.net/sample.xml" target="_blank">http://www.rgraph.net/sample.xml using HTML. <html> <body> <script type="text/javascript"> if (window.XMLHttpRequest) {// code for IE7+, Firefox,... (1 Reply)
Discussion started by: Xperia124
1 Replies

7. Shell Programming and Scripting

Xmllint - Xml-file problem --ods file not opening

Dear All, this is my first post on this Forum, glad to be here. I'm trying to fix an .ods file. Yes, I had a backup, but it's also corrupted. When opening the document I get this EM: read error format error discovered in the file in sub-document content.xml at 2,337040(row,col). So I... (3 Replies)
Discussion started by: jameslast
3 Replies

8. Shell Programming and Scripting

Use curl to send a static xml file using url encoding to a web page using pos

Hi I am try to use curl to send a static xml file using url encoding to a web page using post. This has to go through a particular port on our firewall as well. This is my first exposure to curl and am not having much success, so any help you can supply, or point me in the right direction would be... (1 Reply)
Discussion started by: Paul Walker
1 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. Shell Programming and Scripting

How to know file encoding?

how can i know what format a file is * example: UTF-8 ANSI UCS2 i am in a... (8 Replies)
Discussion started by: tricampeon81
8 Replies
db2x_manxml(1)							     docbook2X							    db2x_manxml(1)

NAME
db2x_manxml - Make man pages from Man-XML SYNOPSIS
db2x_manxml [options] [xml-document] DESCRIPTION
db2x_manxml converts a Man-XML document into one or more man pages. They are written in the current directory. If xml-document is not given, then the document to convert is read from standard input. OPTIONS
--encoding=encoding Select the character encoding used for the output files. The available encodings are those of iconv(1). The default encoding is us-ascii. The XML source may contain characters that are not representable in the encoding that you select; in this case the program will bomb out during processing, and you should choose another encoding. (This is guaranteed not to happen with any Unicode encoding such as UTF-8, but unfortunately not everyone is able to process Unicode texts.) If you are using GNU's version of iconv(1), you can affix //TRANSLIT to the end of the encoding name to attempt transliterations of any unconvertible characters in the output. Beware, however, that the really inconvertible characters will be turned into another of those damned question marks. (Aren't you sick of this?) The suffix //TRANSLIT applied to a Unicode encoding -- in particular, utf-8//TRANSLIT -- means that the output files are to remain in Unicode, but markup-level character translations using utf8trans are still to be done. So in most cases, an English-language doc- ument, converted using --encoding=utf-8//TRANSLIT will actually end up as a US-ASCII document, but any untranslatable characters will remain as UTF-8 without any warning whatsoever. (Note: strictly speaking this is not "transliteration".) This method of con- version is a compromise over strict --encoding=us-ascii processing, which aborts if any untranslatable characters are encountered. Note that man pages and Texinfo documents in non-ASCII encodings (including UTF-8) may not be portable to older (non-international- ized) systems, which is why the default value for this option is us-ascii. To suppress any automatic character mapping or encoding conversion whatsoever, pass the option --encoding=utf-8. --list-files Write a list of all the output files to standard output, in addition to normal processing. --output-dir=dir Specify the directory where the output files are placed. The default is the current working directory. This option is ignored if the output is to be written to standard output (triggered by the option --to-stdout). --to-stdout Write the output to standard output instead of to individual files. If this option is used even when there are supposed to be multiple output documents, then everything is concatenated to standard output. But beware that most other programs will not accept this concatenated output. This option is incompatible with --list-files, obviously. --help Show brief usage information and exit. --version Show version and exit. Some man pages may be referenced under two or more names, instead of just one. For example, strcpy(3) and strncpy(3) often point to the same man page which describes the two functions together. Choose one of the following options to select how such man pages are to be gen- erated: --symlinks For each of all the alternate names for a man page, erect symbolic links to the file that contains the real man page content. --solinks Generate stub pages (using .so roff requests) for the alternate names, pointing them to the real man page content. --no-links Do not make any alternative names available. The man page can only be referenced under its principal name. This program uses certain other programs for its operation. If they are not in their default installed locations, then use the following options to set their location: --utf8trans-program=path, --utf8trans-map=charmap Use the character map charmap with the utf8trans(1) program, included with docbook2X, found under path. --iconv-program=path The location of the iconv(1) program, used for encoding conversions. NOTES
The man pages produced should be compatible with most troff implementations and other tools that process man pages. Some backwards-compat- ible groff(1) extensions are used to make the output look nicer. AUTHOR
Steve Cheng <stevecheng@users.sourceforge.net>. SEE ALSO
The docbook2X manual (in Texinfo or HTML format) fully describes how to convert DocBook to man pages and Texinfo. Up-to-date information about this program can be found at the docbook2X Web site <http://docbook2x.sourceforge.net/> . The input to db2x_manxml is defined by the XML DTD present at dtd/Man-XML in the docbook2X distribution. docbook2X 0.8.8 3 March 2007 db2x_manxml(1)
All times are GMT -4. The time now is 06:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy