On Fri, 2 Feb 2001, Stas Bekman wrote:
> On Tue, 30 Jan 2001, Geoffrey Young wrote:
>
> > sorry again for all the confusion with this morning's digest (I do code more
> > carefully than I write, really I do...)
> >
> > this does present the opportune time to ask the list about the future of
> >
On Tue, 30 Jan 2001, Geoffrey Young wrote:
> sorry again for all the confusion with this morning's digest (I do code more
> carefully than I write, really I do...)
>
> this does present the opportune time to ask the list about the future of
> this digest...
>
> currently, the digest does not have
On Wed, Jan 31, 2001 at 10:34:15AM +, Matt Sergeant wrote:
> I now have a stylesheet that will generate "good enough" POD that
> Pod::Text generates reasonable output. Sadly Pod::Text needs a filename or
> STDIN (we may be able to fudge it to work on a temp filehandle), which
> makes the codin
On Wed, 31 Jan 2001, Andrew Ho wrote:
> MS>But it has to be as easy as uploading one version, and the take23 CMS
> MS>automatically sending out an email to the list. Anything else isn't
> MS>worth it.
>
> I think you're being unfair here; it's impossible for it to be exactly as
> easy given that
Hello,
MS>Mailing a link is easy, converting to a format that looks almost exactly
MS>like the current version Geoff sends out is a bit harder (yes, I can
MS>spawn lynx, which gets most of the way there, but its all coding that
MS>has to be done).
I think the point is emphatically NOT that it h
On Tue, 30 Jan 2001, David Harris wrote:
>
> > Looks like I can get a lot closer with Pod::Text, the sad thing is that
> > Pod::Text can't read from anything but a file. *sigh*
>
> That's what /proc/self/fd/0 in Linux is for. :-)
>
> $ ps | cat /proc/self/fd/0
> PID TTY TIME CMD
> 1608
> Looks like I can get a lot closer with Pod::Text, the sad thing is that
> Pod::Text can't read from anything but a file. *sigh*
That's what /proc/self/fd/0 in Linux is for. :-)
$ ps | cat /proc/self/fd/0
PID TTY TIME CMD
16085 pts/600:00:00 bash
18434 pts/600:00:00 ps
18435
Matt Sergeant <[EMAIL PROTECTED]> writes:
> On Tue, 30 Jan 2001, Robin Berjon wrote:
>
> > At 13:54 30/01/2001 +, Matt Sergeant wrote:
> > >On Tue, 30 Jan 2001, [EMAIL PROTECTED] wrote:
> > >> Seriously - it should be possible to create a XSLT stylesheet that
> > will
> > >>out
On Tue, 30 Jan 2001, Robin Berjon wrote:
> At 13:54 30/01/2001 +, Matt Sergeant wrote:
> >On Tue, 30 Jan 2001, [EMAIL PROTECTED] wrote:
> >> Seriously - it should be possible to create a XSLT stylesheet that
> will
> >>output plain-text, then use XML::Sablotron or one of the oth
On Tue, 30 Jan 2001, Robin Berjon wrote:
> At 13:54 30/01/2001 +, Matt Sergeant wrote:
> >On Tue, 30 Jan 2001, [EMAIL PROTECTED] wrote:
> >> Seriously - it should be possible to create a XSLT stylesheet that
> will
> >>output plain-text, then use XML::Sablotron or one of the oth
At 13:54 30/01/2001 +, Matt Sergeant wrote:
>On Tue, 30 Jan 2001, [EMAIL PROTECTED] wrote:
>> Seriously - it should be possible to create a XSLT stylesheet that
will
>>output plain-text, then use XML::Sablotron or one of the other
>processors
>>to generate the text from
On Tue, 30 Jan 2001, John BEPPU wrote:
> [ date ] 2001/01/30 | Tuesday | 01:50 PM
> [ author ] G.W. Haywood <[EMAIL PROTECTED]>
>
> > > unfortunately, there is no easy way to derive a decent plain text
> > > version from an XML base...
> >
> > !!!??? That's just plain ridiculous.
>
> I agree.
* at 30/01 14:01 + [EMAIL PROTECTED] said:
>
> >Sadly thats not the case. XSLT is not well suited to the task of
> >outputting text documents. It has no facilities for doing things like page
> >widths, indenting, bullet points, etc, for plain text. I have tried this,
> >with the source of the
[ date ] 2001/01/30 | Tuesday | 01:50 PM
[ author ] G.W. Haywood <[EMAIL PROTECTED]>
> > unfortunately, there is no easy way to derive a decent plain text
> > version from an XML base...
>
> !!!??? That's just plain ridiculous.
I agree. If there's going to be an HTML version of it somewher
>Sadly thats not the case. XSLT is not well suited to the task of
>outputting text documents. It has no facilities for doing things like page
>widths, indenting, bullet points, etc, for plain text. I have tried this,
>with the source of the digests being in XHTML, but its harder than it
>fir
On Tue, 30 Jan 2001, [EMAIL PROTECTED] wrote:
>
> > but unfortunately, there is no easy
> > way to derive a decent plain text version from an XML base...
>
> Hmmm. converting one text format to another. Sounds like a job for perl
>;-)
>
> Seriously - it should be possible to c
Hi Geoff,
On Tue, 30 Jan 2001, Geoffrey Young wrote:
> this does present the opportune time to ask the list about the future of
> this digest...
> unfortunately, there is no easy way to derive a decent plain text
> version from an XML base...
!!!??? That's just plain ridiculous.
> thus, the
> but unfortunately, there is no easy
> way to derive a decent plain text version from an XML base...
Hmmm. converting one text format to another. Sounds like a job for perl
;-)
Seriously - it should be possible to create a XSLT stylesheet that will
output plain-text,
My vote is to keep a plain text version available. I don't use an
html-capable mail reader, so sending a link normally means "I'll save this
and read it later when I have time", which often means I'll delete it
three weeks later in cleaning out my 'READ' mail file...
I like the text version bec
Geoffrey Young <[EMAIL PROTECTED]> writes:
> currently, the digest does not have a HTML home. Matt at take23.org has
> graciously agreed to host it and work on the XML stylesheets required for
> the site. This is a very good thing - but unfortunately, there is no easy
> way to derive a decent
I think I personally wouldn't be that much informed as now. I'm too lazy
surfer. Don't know bout the others though. But once a month I have to
check that page then to be informed :P I think the new versions would show
up in list letter's headings too.
Tervisi,
Antti
> how does this str
sorry again for all the confusion with this morning's digest (I do code more
carefully than I write, really I do...)
this does present the opportune time to ask the list about the future of
this digest...
currently, the digest does not have a HTML home. Matt at take23.org has
graciously agreed
22 matches
Mail list logo
