unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: rms@gnu.org
Cc: MON KEY <monkey@sandpframing.com>, jasonr@gnu.org, emacs-devel@gnu.org
Subject: Re: DocView now supports OpenDocument & MS Office formats
Date: Mon, 03 Jan 2011 09:42:23 +0100	[thread overview]
Message-ID: <87sjxa2xao.fsf@member.fsf.org> (raw)
In-Reply-To: <E1PZW9G-0000HT-4j@fencepost.gnu.org> (Richard Stallman's message of "Sun, 02 Jan 2011 17:11:34 -0500")

Richard Stallman <rms@gnu.org> writes:

Hello Richard,

Looking at the homepage and its description, is basically looks like an
approach to make OpenOffice.org functionality available to other
languages (and also remotely to other processes).

,----[ http://udk.openoffice.org/ ]
| Uno stands for Universal Network Objects.  Uno is one of the accepted
| projects of OpenOffice.org.
| 
| Uno is the component model of OpenOffice.org.  Uno offers
| interoperability between programming languages, other components
| models and hardware architectures, either in process or over process
| boundaries, in the Intranet as well as in the Internet. Uno components
| may be implemented in and accessed from any programming language for
| which a Uno implementation (AKA language binding) and an appropriate
| bridge or adapter exists.
`----

I don't know about the consequences with respect to software freedom
here.  OO.org is LGPL, so there might be a chance that proprietary
components leveraging OO.org functionality are now easier to write with
UNO.  But that would only be the case if accessing OO.org functionality
(possibly remotely) via UNO bindings is fundamentally different from
accessing OO.org functionality in C.

>      - asking Emacs users to install the python/pyuno/UNO/OpenOffice/Java
>        dependencies just to gain ODF support is ironic given the extent to
>        which the Emacs-Devels have endeavored to keep the Emacs footprint
>        small;
>
> People who want to use ODF need to install OpenOffice anyway, so I am
> not sure this is a terrible problem.

Well, there are other free office suites that handle ODF as well, like
KOffice.

> If there's another way to do the job, it might be better.

The reason I chose unoconv/OO.org is that it required only a few lines
of elisp to allow for viewing anything OO.org can read inside emacs.

And doc-view doesn't add any hard dependencies at all.  If the required
tools for some kind of document are not installed, or emacs has been
compiled without PNG support, or if the current emacs frame is a TTY
frame, then doc-view falls back to the mode that would be used if there
was no doc-view.

Bye,
Tassilo



  parent reply	other threads:[~2011-01-03  8:42 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 22:32 DocView now supports OpenDocument & MS Office formats MON KEY
2010-12-30 22:59 ` Jason Rumney
2010-12-31  2:12   ` MON KEY
2010-12-31  8:35     ` Tassilo Horn
2010-12-31  9:25       ` Eli Zaretskii
2010-12-31 11:33         ` Tassilo Horn
2011-01-02  0:33     ` Richard Stallman
2011-01-02  7:29       ` MON KEY
2011-01-02 22:11         ` Richard Stallman
2011-01-03  4:14           ` Stephen J. Turnbull
2011-01-04  4:08             ` Richard Stallman
2011-01-04  4:35               ` Drew Adams
2011-01-04  5:33               ` Stephen J. Turnbull
2011-01-03  8:25           ` MON KEY
2011-01-04  4:08             ` Richard Stallman
2011-01-03  8:42           ` Tassilo Horn [this message]
2011-01-04  4:08             ` Richard Stallman
2011-01-04  7:38               ` Tassilo Horn
2011-01-04  8:18                 ` Eli Zaretskii
2011-01-04  9:00                   ` Tassilo Horn
2011-01-04 11:58                     ` Eli Zaretskii
2011-01-05 19:42                   ` Eduard Wiebe
2011-01-06 18:42                     ` Richard Stallman
2011-01-07 11:18                       ` Eli Zaretskii
2011-01-08 21:54                         ` Eduard Wiebe
2011-01-09  4:02                           ` Eli Zaretskii
2011-01-09 20:00                           ` Richard Stallman
2011-01-09 20:13                             ` Eduard Wiebe
2011-01-04 20:36                 ` Richard Stallman
2011-01-04 21:07                   ` Jambunathan K
2011-01-05 15:04                     ` Tom Tromey
2011-01-04 21:17                   ` Tassilo Horn
2011-01-05  2:02                     ` Stephen J. Turnbull
2011-01-05  7:38                       ` Tassilo Horn
2011-01-05 12:11                         ` Stephen J. Turnbull
2011-01-20  7:32                         ` Kevin Rodgers
2011-05-06 12:53                         ` Jambunathan K
2011-01-05 23:37                     ` Richard Stallman
2011-01-06  7:19                       ` Tassilo Horn
2011-01-04 21:52               ` Lennart Borgman
2011-01-05  5:23               ` Miles Bader
2011-01-05  7:40                 ` Tassilo Horn
2011-05-06 14:01               ` Jambunathan K
2011-01-03 13:04           ` CHENG Gao
2011-01-03 14:14             ` Tassilo Horn
2011-01-04  4:07             ` Richard Stallman
2011-01-02 22:11         ` Richard Stallman
2010-12-31  8:08   ` Tassilo Horn
2010-12-31 16:43 ` Stefan Monnier
2011-01-01  0:06   ` MON KEY
  -- strict thread matches above, loose matches on Subject: below --
2010-12-30 14:07 Tassilo Horn
2010-12-30 14:30 ` Drew Adams
2010-12-30 14:50   ` Tassilo Horn
2010-12-30 15:40     ` Stefan Monnier
2010-12-30 15:48       ` Tassilo Horn
2010-12-30 16:04         ` Stefan Monnier
2010-12-30 18:10           ` Tassilo Horn
2011-05-06 15:30       ` Jambunathan K
2011-05-06 16:09         ` Tassilo Horn
2010-12-30 15:22 ` Tassilo Horn
2010-12-30 16:02   ` Stefan Monnier
2010-12-30 17:20     ` Tassilo Horn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjxa2xao.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=monkey@sandpframing.com \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).