Just to clarify, I think this is only possible when using XML (as in the
example script). This is one item that favors using XML instead of the
current method.
On Mon, Apr 25, 2005 at 04:07:37PM +0300, Christoffer Landtman wrote:
> David Everly wrote:
> > On Mon, Apr 25, 2005 at 12:17:33PM +0300, Christoffer Landtman
> > wrote:
> >
> > >PHP-YAZ itself is not able to change the encoding of the records,
> > >so unless the server supports sending the records in another
> > >charset, I'm not entirely sure what is the best way to proceed. We
> > >are experiencing identical issues with some of our Finnish
> > >proprietary servers, and have not yet figured out the best way to
> > >proceed. Setting up a YAZProxy is one solution, but this might seem
> > >a bit overkill.
> >
> >
> > Please correct me if I'm wrong, but if we used the XML features of
> > PHP-YAZ, I think this is possible as follows (in this case,
> > converting from marc-8 to utf-8):
> >
> > yaz_record($id, 1, 'array2; charset=marc-8,utf-8')
> >
> > Or am I confused as to what this is doing?
>
> This is something that I did not know about. I have been testing it
> with yaz_connect(), i.e. giving the charset attribute, but nothing
> happened, so I assumed that this was a lost case.
>
> Apparently this trick only works with the "structured" records, i.e.
> string or raw dont seem to be affected by these.
>
> Nevertheless, nice trick, and I'll test it!
--
Encrypted Mail Preferred:
Key ID: 8527B9AF
Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF
Information: http://www.gnupg.org/
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
|
