Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

XML [accents] ISO-8859-1 auto conv to UTF8 but ...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • XML [accents] ISO-8859-1 auto conv to UTF8 but ...

    Hi !
    I'm experiencing some problems using SSH Read/File Write
    Using Mirth 1.6.1.2750
    Here is my channel def :
    incoming Data : XML
    Channel Source
    - SFTP Reader / File type : ASCII
    - Strip namespace from messages => unchecked
    - Encoding source : ISO-8859-1

    Destination :
    - Connector type : File Writer / File type : ASCII
    - Encoding source : ISO-8859-1

    Every message like this :
    Code:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <mydata>
     <test1>é</test1>
     <test2>à</test2>
    </mydata>
    Is automatically converted into this without reencoding accents ... : :angry: :blink:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <mydata>
     <test1>?</test1>
     <test2>?</test2>
    </mydata>
    :sick:

    I've seen something on the forum in relation with the mirth.properties file that said to add this directive :
    ca.uhn.hl7v2.llp.charset=ISO-8859-1
    (Maybe only for the LLP channels ... but how to fix it for all the system ...)
    Does it really works ? :dry:
    Is there a way to fix this ?

    I know that i'm not the only using accents ...

    That's really a big problem ... :-(

    PLEASE HELP !

    Antaris

  • #2
    Re:XML [accents] ISO-8859-1 auto conv to UTF8 but

    Hi, Antaris.

    This could be perhaps a problem related to the SFTP reader. Please, could you confirm than the same hapends with a File Reader ?

    Please, could you post (as attachements) the source files you're having problems with ?

    The .properties is for older versions of Mirth. Has nothing to do with >1.5 versions.

    Comment


    • #3
      Re:XML [accents] ISO-8859-1 auto conv to UTF8 but

      Hi albertosaez

      Yes, i can confirm it ... unfortunately
      For the attachment, i can't post it on the forum because it contains medical data.
      But, if you just use this little examples it does the same result.

      Do you have an idea of what's going on ? (Due to the Sax Parser ???)

      Maybe i have solved my problem by forcing the sender to give UTF-8 formated messages ; and only in this case, it "works" i've my got accented characters (with the same parameters that i give in the post :blink: )

      I think that there's still a bottleneck inside ... :S

      Doctor is it serious ?


      See you later !

      Antaris

      Again albertosaez thanks for your support. (very active on the forum ... i see)

      Post edited by: Antaris, at: 03/28/2008 09:27

      Comment


      • #4
        Re:XML [accents] ISO-8859-1 auto conv to UTF8 but

        Hi Antaris,

        Just to clarify, do you have the same problem when using the File Reader?
        Gerald Bortis | Chief Information Officer | Mirth Corporation

        Comment


        • #5
          Re:XML [accents] ISO-8859-1 auto conv to UTF8 but

          I've made some test.

          The SFTP plugin for 1.6.1 doesn't recognizes different encodings. But all my tests with normal file reader are OK. The problem only affect to FTP and SFTP readers.

          I've prepared a patch. You could give it a try. (Be sure than 'batch processing' is set to 'No')

          The bug is solved for 1.7.0 sftp_reader.zip (22638 bytes)

          Post edited by: albertosaez, at: 03/29/2008 04:00

          Comment


          • #6
            I am facing the same problem with below PID segment.

            PID|1||ABC304916^^^MRN3^MRN3||INTéGRATéD^ICDTWELVE ||19831230|M||O|

            I wrote below code in Destination transformation but didn't work please help

            var PID52 = msg['PID']['PID.5']['PID.5.2'].toString();
            PID52 = java.lang.String(PID52).replaceAll("é","E");
            msg['PID']['PID.5']['PID.5.2']= PID52.toString();

            Mirth Version 2.1.5490
            Sunny
            Mirth User

            Comment

            Working...
            X