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. On Wed, Jan 28, 2015 at 3:12 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > Tim, > > The original generation is not generating the BOM leader. To my knowledge, > for UTF-8 it was not needed, which seems to be the case, if we believe > this > <http://stackoverflow.com/questions/2223882/whats-different-between-utf-8-and-utf-8-without-bom> > . > > When I open the files in Oxygen 16, I get no error relating to BOM. And I > don't see anything unusual opening with gvim (unix mode/utf-8) on Windows. > > I'll have a Linux build of some of these XML related changes up in a day > or so, you may be able to test the output more directly there. > > - thomas > > On 28/01/2015 16:40, Timothy W. Cook wrote: > > Any one getting a BOM character encoding error when using oXygen or > similar editor to open the files from the wiki can select to replace the > marker. Apparently the file was edited with something that saved it marked > as UTF-8 but used another BOM character. Probably a MS Windows editor, may > the archetype workbench? > > > > On Wed, Jan 28, 2015 at 10:52 AM, Thomas Beale < > thomas.beale at oceaninformatics.com> wrote: > >> >> For those interested, I have added a new version of the XML OPT >> <https://openehr.atlassian.net/wiki/display/ADL/ADL+2+Operational+Template> >> for the demonstration template. This converts more of that AOM class >> properties to XML attributes, reducing size a bit, and arguably improving >> processability. The XML of the core definition in this style looks as >> follows: >> >> >> >> I encourage XML specialists to have a look at these formats and suggest >> improvements (preferably on the wiki page). >> > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- ============================================ Timothy Cook LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook MLHIM http://www.mlhim.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150128/f02bcfd8/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 22860 bytes Desc: not available URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150128/f02bcfd8/attachment-0001.png>
