From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.devel Subject: Re: DocView now supports OpenDocument & MS Office formats Date: Thu, 20 Jan 2011 00:32:44 -0700 Message-ID: References: <87hbduhno4.fsf@gnu.org> <87sjxa2xao.fsf@member.fsf.org> <878vz1dsox.fsf@member.fsf.org> <877hekpdvz.fsf@member.fsf.org> <877hekhzue.fsf@uwakimon.sk.tsukuba.ac.jp> <878vyz3imf.fsf@member.fsf.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1295508803 7855 80.91.229.12 (20 Jan 2011 07:33:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 20 Jan 2011 07:33:23 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 20 08:33:17 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Pfp17-0004zC-Fh for ged-emacs-devel@m.gmane.org; Thu, 20 Jan 2011 08:33:13 +0100 Original-Received: from localhost ([127.0.0.1]:39138 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pfp16-0006PX-Tm for ged-emacs-devel@m.gmane.org; Thu, 20 Jan 2011 02:33:13 -0500 Original-Received: from [140.186.70.92] (port=51302 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pfp0o-0006Nn-4n for emacs-devel@gnu.org; Thu, 20 Jan 2011 02:32:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pfp0l-0003Cn-HJ for emacs-devel@gnu.org; Thu, 20 Jan 2011 02:32:53 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:55185) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pfp0l-0003Cg-7p for emacs-devel@gnu.org; Thu, 20 Jan 2011 02:32:51 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Pfp0j-0004oI-Mu for emacs-devel@gnu.org; Thu, 20 Jan 2011 08:32:49 +0100 Original-Received: from c-24-8-96-241.hsd1.co.comcast.net ([24.8.96.241]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Jan 2011 08:32:49 +0100 Original-Received: from kevin.d.rodgers by c-24-8-96-241.hsd1.co.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Jan 2011 08:32:49 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 27 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-24-8-96-241.hsd1.co.comcast.net User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 In-Reply-To: <878vyz3imf.fsf@member.fsf.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:134805 Archived-At: On 1/5/11 12:38 AM, Tassilo Horn wrote: > "Stephen J. Turnbull" writes: >> > But I think that conversion from and to ODF is not the right approach to >> > support ODF editing in Emacs. Imagine a colleague sends you an ODF file >> > she created using LibreOffice, you convert it to something Emacs can >> > handle, >> >> Uh, just teach jka-compr or crypt++ that it's a zipfile, and what >> you'll see in the buffer is XML, no? Since when is Emacs handicapped >> w.r.t. XML? > > No, you got me wrong. Emacs already figures out it's a zip file, and of > course you can edit the content.xml in it (which is horrible slow, > because all the XML is on one line). Maybe, one might need to update > some metadata as well, who knows, but that should be doable. Maybe insert newlines when reading the XML in and delete them when writing it out. (Newlines can safely be inserted before start-tags within element content.) > My concern was converting ODF to some more human-editable format like > LaTeX or DocBook. And here, converting forth and back has a high > potential to lead to data loss for things the converters cannot handle, > like OpenDocument spreadsheets embedded in text documents. -- Kevin Rodgers Denver, Colorado, USA