From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ruslan Kosolapov Subject: Re: agenda csv export: three problems (batch, koi8-r and commas) Date: Thu, 31 May 2007 19:59:24 +0700 Message-ID: <87bqg1174j.fsf@kosolapov-nb.plesk.ru> References: <87y7j51h4a.fsf@kosolapov-nb.plesk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HtkFU-0002Ed-Qp for emacs-orgmode@gnu.org; Thu, 31 May 2007 08:59:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HtkFT-0002EB-C4 for emacs-orgmode@gnu.org; Thu, 31 May 2007 08:59:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HtkFT-0002E5-2p for emacs-orgmode@gnu.org; Thu, 31 May 2007 08:59:27 -0400 Received: from gw-swsoft2.ll-nsk.zsttk.ru ([82.200.65.190] helo=mail3.plesk.ru) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HtkFS-0000th-5v for emacs-orgmode@gnu.org; Thu, 31 May 2007 08:59:26 -0400 Received: from kosolapov-nb.plesk.ru (unknown [192.168.62.133]) by mail3.plesk.ru (Postfix) with ESMTP id A721B1A9CE2 for ; Thu, 31 May 2007 19:59:24 +0700 (NOVST) In-Reply-To: (Jason F. McBrayer's message of "Thu, 31 May 2007 08:27:32 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org >> org-mode 4.75, emacs-snapshot (latest from debian sid) >> --[ 3. Problems with , and "" ]-- >> As far as I know, strings in csv should be quoted, else there will be >> problems if string contains comma. >> Now I see than "head" field placed in csv without quotes. So, if I >> use comma in heading text, csv-parsing script fails. JFM> I wondered about this immediately after csv agenda export was JFM> added, so I tested it. My testing showed that commas in JFM> headlines are converted to semicolon on export (it must be JFM> getting done earlier in the code than where you looked at it JFM> being placed in the csv). Probably not The Right Thing, but JFM> good enough, and surely easier than worrying about quoting. Yes, I already found org-agenda-export-csv-mapper. Shame on me :( PS: this is strange, but when I test this issue, I didn't see such substitution. Now I can not repeat that case, all works fine. Maybe bug was in my eyes. -- Ruslan Kosolapov Plesk QA Department Second Manager SWsoft, Inc.