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

List:       koffice
Subject:    [Bug 75799] koconverter: output to stdout
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2004-02-23 15:54:01
Message-ID: 20040223155401.20107.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=75799      




------- Additional Comments From nicolasg snafu de  2004-02-23 16:53 -------
On Monday 23 February 2004 15:27, zander kde org wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=75799
>
>
>
>
> ------- Additional Comments From zander kde org  2004-02-23 15:27 -------
> Note that those tools (tar etc) listen to the encoding defined by the user
> (using an environment var)

?

Where do you see an encoding in:

tar -cvf - * | bzip2 -c - > file,tar.bz2

(Yes, I know, nowadays tar can do bzip2 with parameters and you do not need a 
pipe anymore.)

>
> Doing this kind of re-coding adds a lot of complexity..

Why re-coding?

>
> CSV is not a latin1 or even an ASCII defined standard IIRC since you can
> still type unicode characters (Chinese...) which should be encoded.

Selecting the encoding of CSV is a wish and we will need to give the 
possibilty to select it non-interactively. (That is part of supporting a 
batch mode for the filters.)

>
> All in all; its a lot harder then just dumping input.

If you can drop it to a file, you can put it through a pipe too. If the next 
tool that you use cannot cope with the file format (e.g. with the encoding) 
you will have a problem anyway whatever you use a temporary file or a pipe.

>
> I agree with David that this is not a good idea.  You did not answer Davids
> question why this should stay open, I'd like to know that as well.

Koconcverter is a tool for power users. Normal users will never touch it 
anyway. But power users know pipes and would prefer being able to use stdin 
and stdout with it. (And personally, I had to implement the raw filw support 
in the KWord 1.3 import filter just because I could not use stdin with 
koconverter. In this case I would have create a ZIP or TAR file on the fly.)

Also pipes permits the reading program to start processing when the writing 
program is still writing. That is something that you cannot do with temp 
files. (However currently koconverter would need temp files to support stdin 
and stdout, so it has little sence to support it so. Otherwise I would have 
implented it already months ago.)

Have a nice day!

> ____________________________________
> koffice mailing list
> koffice mail kde org
> To unsubscribe please visit:
> https://mail.kde.org/mailman/listinfo/koffice
____________________________________
koffice mailing list
koffice@mail.kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice
[prev in list] [next in list] [prev in thread] [next in thread]