What’s new in 5.6.4
- Several new built-in methods added to the translator API
- The sample data editor now escapes line feeds and displays them as “\r”, “\n” or “\r\n”
- New get_milestone function in the Channel API, it returns the list of milestones for a project
- One bug fix, and one behavior change
- To see the complete list of changes, feel free to browse the Iguana change log
Several new built-in methods added to the translator API [top]
New methods:
- chm.fromXML: Invokes a Chameleon style conversion of XML into HL7
- chm.toXML: Invokes a Chameleon style conversion HL7 into XML
- filter.zip.inflate: Returns a lua table containing decompressed files
- iguana.status: Returns an XML summary of Iguana runtime state
- iguana.webInfo: Returns a Lua table listing Iguana web server and HTTP channel configuration
The sample data editor now escapes line feeds and displays them as “\r”, “\n” or “\r\n” [top]
The way the sample data editor treats line endings has been updated. They are now displayed as visible tokens, which gives you greater control over the exact structure of your sample data. These line endings vary depending on the system you are using, but now they will always be displayed so you can see exactly what is happening.
For example:
- In Windows text files, the end of a line is marked with \r\n
- In Unix-like environments (including Macs), the traditional line end in a text file is a single \n
- In an HL7 message, lines end with a single \r, and the message itself ends with \r\n
- In HTTP requests, each line of the header ends with \r\n
This is a sample HL7 message:
