Thanks Chris!
Well, before i did anything else, i did hop over to the web archives and found
my post was there soon after i sent it on the 1st, so i thought i was posting
to the right list. In any case, i will try the new e-mail address.
This also means the translate site needs to be corrected/
> I prepared two commits for koha to force the use of the LibXML parser.
> Can you test them and apply them if they are ok ? (I only greped for
> any occurrences of XML::Simple and MARC::File::XML and add the correct
> line). Both commits are available at the top of my wip-for-upstream
> branc
On Mon, Dec 8, 2008 at 7:17 PM, Krishnan Mani <[EMAIL PROTECTED]> wrote:
> Sorry to intrude, but i am sending this out to the dev list to check if
> anyone knows who's running the translate list.
>
> i sent the e-mail below to the translate list on 1st December, then wrote to
> the list admin on th
Sorry to intrude, but i am sending this out to the dev list to check if anyone
knows who's running the translate list.
i sent the e-mail below to the translate list on 1st December, then wrote to
the list admin on the 4th, but haven't received a response yet.
BTW, i can volunteer to run the tra
Vincent Danjean a écrit :
> Frederic Demians wrote:
>
And if we know where the XML parser is called (directly or indirectly),
we can set in the koha file(s) the global variable
>> $XML::SAX::ParserPackage = "XML::LibXML::SAX";
>>
in order to forc
Frederic Demians wrote:
>>> And if we know where the XML parser is called (directly or indirectly),
>>> we can set in the koha file(s) the global variable
> $XML::SAX::ParserPackage = "XML::LibXML::SAX";
>>> in order to force the good XML parser without requiring to modify a
>>> global configur
On Mon, Dec 8, 2008 at 6:42 AM, Vincent Danjean <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Henri-Damien LAURENT wrote:
>> Hi,
>> I am glad to announce String Freeze for 3.0.1.
>> Translators, you have 3 week time for translations.
>> It should be only differences from 3.0.0
>> But strings Normalization
>> And if we know where the XML parser is called (directly or indirectly),
>> we can set in the koha file(s) the global variable
$XML::SAX::ParserPackage = "XML::LibXML::SAX";
>> in order to force the good XML parser without requiring to modify a
>> global configuration file
> Primarily, Koha
On Sun, Dec 7, 2008 at 11:53 AM, Vincent Danjean <[EMAIL PROTECTED]> wrote:
> Joshua Ferraro wrote:
>> I can say with certainty that Expact is not UNICODE safe, neither is
>> PurlPerl ... only LibXML is safe.
>
> In this case, do you know which part of Koha really call the XML parser ?
> As said be
Hi,
Henri-Damien LAURENT wrote:
> Hi,
> I am glad to announce String Freeze for 3.0.1.
> Translators, you have 3 week time for translations.
> It should be only differences from 3.0.0
> But strings Normalization sometimes did many tiny changes.
> Sorry about that.
>
> Chris will tell you more a
Joshua Ferraro wrote:
> I can say with certainty that Expact is not UNICODE safe, neither is
> PurlPerl ... only LibXML is safe.
In this case, do you know which part of Koha really call the XML parser ?
As said before:
I failed to see where koha really instantiate a sax parser.
'rgrep "u
Hi all,
I can say with certainty that Expact is not UNICODE safe, neither is
PurlPerl ... only LibXML is safe.
Cheers,
Josh
On Sun, Dec 7, 2008 at 3:33 AM, Vincent Danjean <[EMAIL PROTECTED]> wrote:
> I forgot the CC
>
> Original Message
> Subject: Re: [Koha-devel] [Koha] Wron
I forgot the CC
Original Message
Subject: Re: [Koha-devel] [Koha] Wrong SAX Parser - does it matter? -> impact
on Debian packaging
Date: Sun, 07 Dec 2008 09:31:03 +0100
From: Vincent Danjean <[EMAIL PROTECTED]>
To: Chris Cormack <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]
13 matches
Mail list logo
