On Wednesday, March 26, 2003, at 10:02 PM, Kip Hampton wrote:
S Woodside wrote:
To add to this, sorry for the spam but I think this is
relevant/important. A lot of the discussion on this list seems to
assume that those involved consider modifying the AxKit code itself
to be a reasonable soluti
S Woodside wrote:
To add to this, sorry for the spam but I think this is
relevant/important. A lot of the discussion on this list seems to assume
that those involved consider modifying the AxKit code itself to be a
reasonable solution ... to me that's just not an option. Sure, I could
probably
On Wed, Mar 26, 2003 at 06:53:38PM -0500, S Woodside wrote:
> To add to this, sorry for the spam but I think this is
> relevant/important. A lot of the discussion on this list seems to
> assume that those involved consider modifying the AxKit code itself to
> be a reasonable solution ... to me t
To add to this, sorry for the spam but I think this is
relevant/important. A lot of the discussion on this list seems to
assume that those involved consider modifying the AxKit code itself to
be a reasonable solution ... to me that's just not an option. Sure, I
could probably do it (after a wee
Well, part of my frustration is generally that the axkit user/developer
base is small. Smaller than it should be IMHO (I can't comment on why
that might be true for the developer base but there doesn't seem to be
as much user understanding of what a userful tool it is).
simon
On Wednesday, Mar
On Wednesday, Mar 26, 2003, at 22:30 Europe/London, S Woodside wrote:
> Anyway, I guess that 1.6.1 doesn't really work on debian 2.2, is the
> upshot.
I wouldn't go that far. I suspect it can be made to work.
Sure, with hours of hacking as I don't have root so I'm going to start
installing everyt
> Anyway, I guess that 1.6.1 doesn't really work on debian 2.2, is the
> upshot.
I wouldn't go that far. I suspect it can be made to work.
Sure, with hours of hacking as I don't have root so I'm going to start
installing everything under the sun lcoally, changing my paths etc. etc.
Along with the
On Wednesday, Mar 26, 2003, at 21:01 Europe/London, Don Shanks wrote:
I have a simple application, or so I think. In writing my dynamic
content website, I notice that 90% of the actiual XML files loaded are
identical. Basically a xml document with some custom XSP tags loads and
all data is pulled
I have a simple application, or so I think. In writing my dynamic
content website, I notice that 90% of the actiual XML files loaded are
identical. Basically a xml document with some custom XSP tags loads and
all data is pulled from a database depending upon the uri requested.
What I would like to
On Wed, 26 Mar 2003, Sebastian Rahtz wrote:
> My argument against XPathScript is that it ties me to Perl
> and AxKit. All the work I do with XSLT could be ported
> trivially to eg Cocoon (spit) if I had to. If I go xps,
> I am tied to a single supplier and framework. No lack
> of faith in the grea
Hi,
I've updated my patch to include the modifications I made during
benchmarking; specifically:
- Fixed an issue in AxKit.pm where I was unnecessarily creating a style
provider before checking the cache validity.
- Added support to Cache.pm for maintaining a copy of dependancy
information in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>>
> ^--- missing ?
>
>Isn't this what the error message is trying to tell you?
You are indeed right. The correct error message with a character
entity is
Malformed UTF-8 character (unexpected non-continuation byte 0x00 after st
[EMAIL PROTECTED] wrote:
...
> Tried:
>
>
^--- missing ?
Isn't this what the error message is trying to tell you?
--
Alan F. Dickey - Interaction and Realization
http://www.intac.com/~afdickey
mailto:[EMAIL PROTECTED]
VOX: 908-273-3232 Cell: 908-334-0932
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 26 Mar 2003 [EMAIL PROTECTED] wrote:
> I just wanted to translate my english AxPoint presentation to german,
> but: No Umlauts!
> So what shall I do? Presentation is tomorrow afternoon, if everything
> fails I have to use P&#x!point...
I hac
Well... Funny :)
It don't give me chance to insert the file... Ok. One
more try (with extension now). Plus dumping it here:
---
diff -Naur test2/i386-linux/Apache/AxKit/Language/XSP/SimpleTaglib.pm
5.8.0/i386-linux/Apache/AxKit/Language/XSP/SimpleTaglib.pm
--
Hi, Everyone.
Please review this patch (for last CVS that I downloaded today)
(again - to minimize warning messages)
Let me know please if my changes there are wrong.
Please take a look to "binmode $fh, ':utf8'". It disables
warnings "Wide character in print at " under Perl5.8...
Will it b
On Wed, 26 Mar 2003, [EMAIL PROTECTED] wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi list,
>
> I just wanted to translate my english AxPoint presentation to german,
> but: No Umlauts!
>
> So what shall I do? Presentation is tomorrow afternoon, if everything
> fails I have to use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
I just wanted to translate my english AxPoint presentation to german,
but: No Umlauts!
Tried:
...
axpoint vortrag_270303.axp > vortrag_270303.pdf
Got:
Only ASCII encoding allowed without perl 5.7.2 or higher. You tried: ISO-8859-1
On Wed, 26 Mar 2003, Nik Clayton wrote:
> Hi all,
>
> [ Could've sworn I'd posted this, but can't find it in the archives ]
>
> The presentation I gave a few weeks ago to the London Perl Mongers group
> about AxKit::App::Gallery is available online.
>
> http://people.freebsd.org/~nik/AxKit-App
Hi,
I've done some basic testing of my patches using ab. I tested both a
single XSLT transform and a double transform (XSLT => XSLT => result).
The result tables are at the end of this email, but in summary:
- Overall
I found that my patches don't introduce any significant performance
issue
Hi all,
[ Could've sworn I'd posted this, but can't find it in the archives ]
The presentation I gave a few weeks ago to the London Perl Mongers group
about AxKit::App::Gallery is available online.
http://people.freebsd.org/~nik/AxKit-App-Gallery.mov
It's a trifle large, and you'll probably
21 matches
Mail list logo
