Re: UTF8 characters in Article Body in TicketGet Response

Hi Juan,

I was able to reproduce the problem please subscribe to bug#8558 in our bugzilla, 
http://bugs.otrs.org/show_bug.cgi?id=8558

This bug was filed some days ago, and seams to be the same problem.

((enjoy))

Carlos Rodríguez




On Jun 20, 2012, at 5:53 AM, Juan Manuel Clavero Almirón wrote:

> Hi all,
> I’m learning how to use Web Services in OTRS.
> One function that we may need is Get ticket info WITH all articles. So I’ve managed to create a new web service with Ticket::TicketGet controller. I’ve succesfully got basic ticket data (queue, type and such).
>  
> But, when I add “<AllArticles>1</AllArticles>” to the request, I get the following error:
>         not well-formed (invalid token) at line 1, column 2328, byte 2328 at C:/strawberry/perl/vendor/lib/XML/Parser.pm line 187
> because there are some accented characters in the body of one of the articles. Both xml request and response start with <?xml version="1.0" encoding="UTF-8"?>
>  
> I’ve made a small change in Kernel/GenericInterface/Operation/Ticket/TicketGet.pm to encode in base64 article subject and body, because they may be written in spanish.
> Isn’t OTRS working in utf8? Shouldn’t the body and subject already be in utf8?
>  
> Kind regards,
> Juan Clavero
>  
> _______________________________________________
> OTRS mailing list: dev - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/dev
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev