On 1/4/06, Ed Summers <[EMAIL PROTECTED]> wrote:
> I would opt for #2. There is a new version of MARC::Charset available
> which should ease the marc8 <-> utf8 charset translation. Shortly
> there will be a new MARC::File::XML that uses the latest MARC::Charset
>
> You might be interested in taking
I would opt for #2. There is a new version of MARC::Charset available
which should ease the marc8 <-> utf8 charset translation. Shortly
there will be a new MARC::File::XML that uses the latest MARC::Charset
You might be interested in taking a look at how Evergreen is storing
MARC data. I know that
In case you haven't already seen the deadline extension... There are
some good presentation topics already. Combined with lightning talks,
and time for mixing/hacking it should be a lot of fun.
--
We have extended the deadline for prepared talk proposals for Code4lib
2006. [1] The new proposal de
Hello all,
Koha v3 will definetly be utf-8 (+ use indexdata zebra as backend for
retrieving records + many other great features).
Most of the stuff for utf-8 seems to be working quite well :
* templates moved to utf-8 (http-equiv)
* translation strings moved to utf-8 (iconv)
* mySQL database (