[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: A few features that I'd like to see in koffice.
From:       "M. Fioretti" <m.fioretti () inwind ! it>
Date:       2003-06-30 4:57:56
[Download RAW message or body]

On Sun, Jun 29, 2003 20:05:00 at 08:05:00PM +0200, Thomas Zander (zander@planescape.com) wrote:

> 
> Did you never print source code? In color?
> I can imagine what Andrew wants being exactly that.  To have sourcecode with
> syntax highlighting, but not only on screen, but also on paper.
> 
I know that source code highlighting is what you just summarized, and
use it. I just doubt about having such a feature in a word processor,
rather than in a programmer text editor (emacs, vi, whatever), at
least in the context specified by the OP.

Reports, assignments and other burocratic stuff doesn't need/want to
have code embedded. In my work experience this is considered boring,
distracting, unprofessional, you name it. If the pointy haired boss
stumps in a C++ page inside the status report, he'll scream like hell.
The code will be attached, and the report will say "we solved the bug
as shown in attachment #1".

Ditto for university project. Long listing are attached at the end, as
separate files/chapters. Of course, if you want to write a programming
book with KOffice is different.

Whatever. My only concern, if any, is that adding this before, for
example, full compatibility with OASIS file formats will enforce the
opinion that KOffice is good just for programming freaks, not as a
general purpose Free Office Suite for general desktop.

	Ciao,
		Marco Fioretti

-- 
Marco Fioretti                 m.fioretti, at the server inwind.it
Red Hat for low memory         http://www.rule-project.org/en/

There is more to life than increasing its speed.  -- Mahatma Gandhi
____________________________________
koffice mailing list
koffice@mail.kde.org
To unsubscribe please visit:
http://mail.kde.org/mailman/listinfo/koffice
[prev in list] [next in list] [prev in thread] [next in thread]