Similar behavior to HTTP::Request->decoded_content would be sufficient to my 
needs. So perhaps XML::Compile::XOP::Include->decoded_content ?

Basically, instead of “<e:value locale="ja">&#x65B0;&#x898F;</e:value>”, I’d 
like to see “<e:value locale="ja">新規</e:value>”.

KP

--
Kit Peters
Doer of Things, ATS Integrations
D: +1 949 793 8208   M: +1 816 200 0279

On 8/17/16, 17:15, "Mark Overmeer" <[email protected]> wrote:

    * Kit Peters ([email protected]) [160817 21:53]:
    > Is there a quick and easy way to decode an XOP attachment? Basically
    > I’d like the Unicode characters therein to come out as characters,
    > not code points.
    
    I am aware of other XOP users, but never got feedback how to
    improve the interface.  Never used it myself, only implemented
    the basic features ;-)
    
    So: you may suggest improvements by showing real-life examples.
    -- 
    Regards,
    
                   MarkOv
    
    ------------------------------------------------------------------------
           Mark Overmeer MSc                                MARKOV Solutions
           [email protected]                          [email protected]
    http://Mark.Overmeer.net                   http://solutions.overmeer.net
    
    

_______________________________________________
Xml-compile mailing list
[email protected]
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/xml-compile

Reply via email to