I have tested sword version 1 and the encoding is correct, UTF-8.
But I need to have my dspace talking with OJS, which uses Sword v2.
Is this a 3.2 bug? I tested demo.dspace.org/swordv2 and the response
encoding is correct. UTF-8.
2015-01-09 16:37 GMT-02:00 Alcides Carlos de Moraes Neto <
alcides.n...@gmail.com>:
> Here is the response header from a wget -S request
>
> HTTP/1.1 200 OK
> Age: 0
> Date: Fri, 09 Jan 2015 18:35:37 GMT
> X-Cache: MISS
> Content-Type: application/atomserv+xml;charset=ISO-8859-1
> Accept-Ranges: bytes
> Content-Length: 241251
> Proxy-Connection: Keep-Alive
>
>
> 2015-01-09 15:58 GMT-02:00 Alcides Carlos de Moraes Neto <
> alcides.n...@gmail.com>:
>
> Hello everyone,
>>
>> I'm trying to use dspace Swordv2 webapp but I'm having encoding issues.
>>
>> Responses from swordv2 on my install have the encoding response header
>> set to ISO-8859-1
>>
>> However, my default.license file has a UTF-8 encoding. After a successful
>> authentication, the response from servicedocument is an invalid XML.
>>
>> What should I do? I cannot find any settings whatsoever regarding the
>> encoding of the swordv2 application.
>>
>
>
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
