From: hermann g. <hgr...@gm...> - 2002-10-16 18:57:10
|
hi Yeshiah, hi 2 all the rest ;-) the extended mode isn't for support of extended chars, it is the mode=20 for supporting the extended csv mode, an extract of the file=20 manual.txt: <cut> The extended CSV mode is similar to the normal CSV mode in that you=20 separate each field using commas and you can use double quotes to=20 protect commas from being interpreted as the field separator.=20 However, the difference comes in when you want to add a double quote=20 into the field. Under the extended CSV mode, you need to preface the=20 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=20 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 |