Hi Vitalije,

Before your reply I had been looking at the leo files in Scite and noticed 
when nodes are created with script to convert lines to nodes, a linefeed is 
added before the </t>, but the last node does not have a line feed before 
</t>  (see body text G, H):
<?xml version="1.0" encoding="utf-8"?>
<!-- Created by Leo: http://leoeditor.com/leo_toc.html -->
<leo_file xmlns:leo="http://leoeditor.com/namespaces/leo-python-editor/1.1"; 
>
<leo_header file_format="2"/>
<globals/>
<preferences/>
<find_panel_settings/>
<vnodes>
<v t="lewis.20200419120026.1"><vh>CSV NEW</vh></v>
<v t="lewis.20200419172940.1"><vh>CSV NEW</vh>
<v t="lewis.20200419172940.2"><vh>LineNumber 0</vh></v>
<v t="lewis.20200419172940.3"><vh>LineNumber 1</vh></v>
<v t="lewis.20200419172940.4"><vh>LineNumber 2</vh></v>
<v t="lewis.20200419172940.5"><vh>LineNumber 3</vh></v>
</v>
</vnodes>
<tnodes>
<t tx="lewis.20200419120026.1">A, B,
C, D
E, F
G, H</t>
<t tx="lewis.20200419172940.1"></t>
<t tx="lewis.20200419172940.2">A, B,
</t>
<t tx="lewis.20200419172940.3">C, D
</t>
<t tx="lewis.20200419172940.4">E, F
</t>
<t tx="lewis.20200419172940.5">G, H</t>
</tnodes>
</leo_file>

Whereas if I create a new node using <Ctrl-i> insert-node command, the 
treatment is only to add the </t>
[snip]
<t tx="lewis.20200419173505.4">E, F
</t>
<t tx="lewis.20200419173505.5">G, H</t>
<t tx="lewis.20200419173516.1">I, J</t>
</tnodes>
</leo_file>

It is this difference which causes the promote-child-bodies script to copy 
the body text back without linefeeds. Would it be more consistent for a 
linefeed to precede </t> always? Why is the last line treated differently?
I am not an expert at all on linefeed terminology so apologies if this is a 
poor suggestion.

Regards
Lewis

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/1a4dbc5b-df61-4aeb-8b94-fcd76ae42532%40googlegroups.com.

Reply via email to