Ah you're right, at the moment I have not turned quoting on of the source text data i.e. what goes between the tags. I think two types of processing is needed - one to do normal XMl quoting (things like '<' to '<' etc) and then a utf-8 conversion that detects wrong characters and hopefully converts them to a UTF-8 equivalent. I think the wrong chars in this template are actually from the demographic templates that Sergio and Rigoleta did a long time ago...
- thomas On 28/01/2015 18:40, Timothy W. Cook wrote: > I didn't state the problem well. The issues is a character in the > file, that is not a UTF-8 character and tools like oXygen think it is > a byte order mark. > I see Ian noticed a similar issue. It really isn't a big deal. > Maybe it happened in the upload? You will only see it depending upon > your settings in oXygen maybe you have IGNORE or REPLACE selected > instead of REPORT? > http://www.oxygenxml.com/doc/ug-editor/index.html#topics/preferences-encoding.html > > > > BOM is mainly used for backwards compatibility with legacy systems, at > this point. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150128/c7ab4bb4/attachment.html>
