Sponsored Content
Top Forums Shell Programming and Scripting Hebrew converted into jibrish while put command Post 303016749 by naamas03 on Thursday 3rd of May 2018 05:16:58 AM
Old 05-03-2018
HI ,
thank you for your quick reply .
First of all when i'm copying the file manually , without the script . the file transfer great. you can see the hebrew in the ftp server.
the problem exists only by transfering it by the script.
I shall emphasis that the script user to work just fine .
Inside the xml file the title is encoding="utf-16"
but maybe the binary mode doesn't cover all the oppurtunity of characters, othere than that I don't see whay it stopped to conver the file successfully .
can you please donate me a little bit info about the "recode" or "iconv"
do i nedd to put it instead of binary or in addition ?
THanks in Advanced
Naama

Last edited by naamas03; 05-03-2018 at 06:34 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

hebrew font for ie5 in sun solaris

somebody know how to install Hebrew font for ie5 for sun solaris and from were (1 Reply)
Discussion started by: goldfelda
1 Replies

2. HP-UX

where to put autorstart command?

hi everyone, I want to run some command automatically when the OS boot. In Linux, I found that we just put it into /etc/rc.local file; but I don't know where to put it in HP-UX system. please, help me........ thanks very much, :) (2 Replies)
Discussion started by: tataxin
2 Replies

3. Shell Programming and Scripting

Grep command is not working when put into cron

Hi, I worte a script which runs perfect when i execute it manually. But when i scheduled into cron the grep command alone is not working. the sample script, /usr/bin/grep FTP $subfile > /tmp/tfsrec.dat tfs=`echo $?` if then echo "FTP FOUND" else echo "FTP NOT FOUND" Where... (5 Replies)
Discussion started by: thiru_cs
5 Replies

4. UNIX for Dummies Questions & Answers

put command issues with a tftp server

From a remote client, I'm trying to create a timestamped directory and put a file inside the directory. The directory and the file are not present already inside the tftp server. If I need to put a file inside a tftp server, which is not existing already what should I need to do.. I face errors... (9 Replies)
Discussion started by: Amudha
9 Replies

5. UNIX for Dummies Questions & Answers

FTP put command problem

Hello,I am trying to put something on the ftp server using the put command. Whenever I try, I get this error: ftp> put SIMS.war local: SIMS.war remote: SIMS.war 200 PORT command successful 553 Can't open that file: Permission denied I have set rwx for all on that file and I still am... (3 Replies)
Discussion started by: mojoman
3 Replies

6. Shell Programming and Scripting

Status of FTP Put command

Can i capture the status of put command after i ftp a file? (4 Replies)
Discussion started by: aixjadoo
4 Replies

7. Shell Programming and Scripting

How to put output of one command into a variable

Hi, Let say I have these 3 files (state, list and myscript). I want to be able get the sample output like below when I run myscript. Any one know how to fix the code? TIA. ~~~~~~~~~~~~~~~ > cat /home/state CA > cat /home/list CA 100 50 20 AUS 120 61 10 > cat myscript... (6 Replies)
Discussion started by: joker_789us
6 Replies

8. Linux

Not able to put ls -lR command in background

Hi All, i am trying to put ls -lRt command to run in the background but it fails. i continue to get output on screen and didnt get the command prompt right after i put the command in background. command i am using is ls -lRt & i am using bash. Can someone let me know how to... (6 Replies)
Discussion started by: omkar.jadhav
6 Replies

9. Shell Programming and Scripting

Shell script variable $1 used with put command

I have the following script used, i am new to shell scripting. tryign to understand. in the put $BASE_FOLDER/$base_name holds which path. What does it mean by $1 second path in put command is it constructing this path: /user/hive/warehouse/stage.db/$1 what is $1 holding in above path. ... (2 Replies)
Discussion started by: cplusplus1
2 Replies

10. Shell Programming and Scripting

Hebrew character convert error while put thru ftp

Hi all , i have a script which cp xml files from linux to other server thru ftp my xml file contains charcters in hebrew . my script is #!/bin/bash HOST="....." USER="....." PASSWORD="..." cd /usr2/app/naama/ filelist='find . -mmin -60 | tail -n +2 | awk -F "/" '{print $2}' | grep xml'... (3 Replies)
Discussion started by: naamas03
3 Replies
db2x_texixml(1) 						     docbook2X							   db2x_texixml(1)

NAME
db2x_texixml - Make Texinfo files from Texi-XML SYNOPSIS
db2x_texixml [options]... [xml-document] DESCRIPTION
db2x_texixml converts a Texi-XML document into one or more Texinfo documents. If xml-document is not given, then the document to convert comes from standard input. The filenames of the Texinfo documents are determined by markup in the Texi-XML source. (If the filenames are not specified in the markup, then db2x_texixml attempts to deduce them from the name of the input file. However, the Texi-XML source should specify the filename, be- cause it does not work when there are multiple output files or when the Texi-XML source comes 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. --info Pipe the Texinfo output to makeinfo(1), creating Info files directly instead of Texinfo files. --plaintext Pipe the Texinfo output to makeinfo --no-headers, thereby creating plain text files. --help Show brief usage information and exit. --version Show version and exit. 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
Texinfo language compatibility. The Texinfo files generated by db2x_texixml sometimes require Texinfo version 4.7 (the latest version) to work properly. In particular: o db2x_texixml relies on makeinfo to automatically add punctuation after a @ref if it it not already there. Otherwise the hyperlink will not work in the Info reader (although makeinfo will not emit any error). o The new @comma{} command is used for commas (,) occurring inside argument lists to Texinfo commands, to disambiguate it from the comma used to separate different arguments. The only alternative otherwise would be to translate , to . which is obviously undesirable (but earlier docbook2X versions did this). If you cannot use version 4.7 of makeinfo, you can still use a sed script to perform manually the procedure just outlined. Relation of Texi-XML with the XML output format of makeinfo. The Texi-XML format used by docbook2X is different and incompatible with the XML format generated by makeinfo(1) with its --xml option. This situation arose partly because the Texi-XML format of docbook2X was de- signed and implemented independently before the appearance of makeinfo's XML format. Also Texi-XML is very much geared towards being ma- chine-generated from other XML formats, while there seems to be no non-trivial applications of makeinfo's XML format. So there is no rea- son at this point for docbook2X to adopt makeinfo's XML format in lieu of Texi-XML. BUGS
o Text wrapping in menus is utterly broken for non-ASCII text. It is probably also broken everywhere else in the output, but that would be makeinfo's fault. o --list-files might not work correctly with --info. Specifically, when the output Info file get too big, makeinfo will decide to split it into parts named abc.info-1, abc.info-2, abc.info-3, etc. db2x_texixml does not know exactly how many of these files there are, though you can just do an ls to find out. 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_texixml is defined by the XML DTD present at dtd/Texi-XML in the docbook2X distribution. docbook2X 0.8.8 3 March 2007 db2x_texixml(1)
All times are GMT -4. The time now is 02:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy