[pilot-db-list] =?iso-8859-1?Q?Re:the_-extended_mode_problem?=

[=?iso-8859-1?Q?<mar...@la...>]

Quickly,

There isn't reason that the tools cut the file in the middle.
I think there is a character in your file that the tool
understand as the end of the file.
The best way is to verify if the database is always cuted at
the same place and look the characters before and after the
cuting.

Salut,
Marc.

> I understand freeware and I am not offended. Just some feedback.
> If I dont use the -e switch I only get an output file of the
first 2kb of a
> 30kb file.
> 
> WITH the -e switch outputs the whole converted file but
converts all
> high-ascii
> over 220 (used for many foreign languages ie hebrew text of
the Old
> Testament) all become \xblah.
> 
> I dont know why the program breaks after 2kb without the -e
switch since I
> dont know what the difference internal to the program is.
BUT WITH the -e
> switch it DOES process the whole file.
> 
> The file DOES contain newlines and requires decoding with
the -e switch.
> Comehow though it needs a way to NOT convert high ascii
chars only those
> under ascii 32.
> 
> Can you impliment this easily? I think it SHOULD be easy.
And perhaps needs
> to be simply fixed in the -e coding.  Extended mode should
NOT convert
> anything over 128 into \xblah at all.
> 
> I can see this as nothing but an accidental bug.
> 
> Patient I am but this does appear simple. My pdb DOES use
extended mode
> characters but the highascii charaters should not be
converted like this but
> pass through as simple characters.
> 
> Yeshiah
> 
> 
> ----- Original Message -----
> From: "hermann griebel" <hgr...@gm...>
> To: "'Yeshiah Zalman'" <ye...@ea...>
> Cc: <pil...@li...>
> Sent: Wednesday, October 16, 2002 7:46 AM
> Subject: RE: [pilot-db-list] the -extended mode problem
> 
> 
> hi Yeshiah, hi 2 all the rest ;-)
> 
> 
> the extended mode isn't for support of extended chars, it is
the mode
> for supporting the extended csv mode, an extract of the file
> manual.txt:
> 
> <cut>
> The extended CSV mode is similar to the normal CSV mode in
that you
> separate each field using commas and you can use double
quotes to
> protect commas from being interpreted as the field separator.
> However, the difference comes in when you want to add a
double quote
> into the field. Under the extended CSV mode, you need to
preface the
> quote mark with a backslash (\) like this:
> </cut>
> 
> btw, i'm using german extended chars (=E4 =F6 =FC =C4 =D6 =DC and =DF),
only two of
> them are converted wrong,  the =F6 (\xf6) and =C4 (\xc4), the
others are
> all right.
> 
> it's freeware, be patient ;-)
> 
> so long, ciao hermann
> 
> 
> -----Original Message-----
> From: Yeshiah Zalman [SMTP:ye...@ea...]
> Sent: Tuesday, October 15, 2002 10:43 PM
> To: pil...@li...
> Subject: [pilot-db-list] the -extended mode problem
> 
> I have a database which uses high-ascii greek.
> When I used pdb2csv to convert it to csv, I get
> one of 2 problems depending on how I convert.
> 
> If I dont use the -e switch for extended chars I get 10%
> of the data. The rest is cut off.
> 
> If I DO use the -extended mode... I get the whole
> file converted but all geek chars are \xblah\xblah
> 
> Neither of these are good outputs. What am I missing here.
> 
> Yeshiah
> 
> 
> 
> 

Acc=E9dez au courrier =E9lectronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 =80/mn) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)"