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 
> <mailto: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).
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150128/93637318/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/93637318/attachment-0001.png>

Reply via email to