# Problem saving in archetype editor

**Category:** [Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)
**Created:** 2014-10-02 11:13 UTC
**Views:** 3
**Replies:** 1
**URL:** https://discourse.openehr.org/t/problem-saving-in-archetype-editor/14332

---

## Post #1 by @siljelb

I’m having trouble saving a particular archetype from Archetype Editor. Other archetypes are apparently saved without issue. I’m getting the following error message. The archetype is attached to this email. I’d be extremely happy if anyone could tell me why this happens and how to fix it… J

<img width="408" height="214" id="Bilde_x0020_1" src="upload://3VENoCHo8dwSwfMZmzR8yHMU3g9.png">

Kind regards,
**Silje Ljosland Bakke**

Coordinator, National Editorial Board for Archetypes, National ICT Norway
Adviser, R&D dept, E-health section, Bergen Hospital Trust

Tel. +47 40203298


[details="(attachments)"]

[openEHR-EHR-EVALUATION.risk.v1.adl|attachment](upload://3AsF1JVfmEmWPatg9etYGHq65vT.adl) (5.53 KB)

[/details]

---

## Post #2 by @Peter_Gummer1

I’m having trouble saving a particular archetype from Archetype Editor\. Other archetypes are apparently saved without issue\. I’m getting the following error message\. The archetype is attached to this email\. I’d be extremely happy if anyone could tell me why this happens and how to fix it… :\)

Hi Silje,

I took a look at the archetype in a text editor \(TextWrangler\) and it’s displaying the entire definition section on one line\. Something is clearly wrong with the line endings in the ADL file, so I did a hex dump of it to have a closer inspection\. This is what the hex dump looks like around the keyword ‘definition’:

0002240      2073    203d    3e3c    0a0d    0a0d    6564    6966    696e
0002260      6974    6e6f    090a    5645    4c41    4155    4954    4e4f

Those two ‘0a0d&#39; pairs on the first line are carriage return\-linefeed pairs, which are normal on Windows\. Then see the ‘0a&#39; on the second line? That’s a linefeed, and there’s no ‘0d&#39; carriage return accompanying it; this is normal on Linux or a Mac\.

So it looks like someone has edited the ADL file in a text editor in way that’s somehow caused a mixture of the two styles of line endings\. The ADL Parser internally normally removes all of the carriage returns before it starts parsing the archetype, but my guess would be that it’s got confused when it encountered this inconsistent formatting within the file\. This has probably caused it to think that almost all of the definition section is inside the first comment in the definition section\!

I would suggest opening the file in a text editor, and then re\-type all of the line endings manually in the definition section\. Then save it again\. Depending on the text editor, hopefully it will save all of the line endings consistently one way or the other for you\. Then try opening it in Archetype Editor again\.

Would you be able to file a problem report for this at http://www.openehr.org/issues/browse/AEPR please?

It would be interesting to know whether the newer ADL Parser in the ADL Workbench also has a problem with this file\.

Peter

---


**Canonical:** https://discourse.openehr.org/t/problem-saving-in-archetype-editor/14332
**Original content:** https://discourse.openehr.org/t/problem-saving-in-archetype-editor/14332