On Friday, February 23, 2018 at 11:35:42 AM UTC-6, Edward K. Ream wrote:
> Afaik, there are few if any problems with other languages.
Just for the record, there is a generic problem with all importers that has
no real solution, namely constructs that look like section references.
Recognizing
many (most?) problems with imports can be fixed by hand in the generated
> @clean tree.
Yes, I am aware of this. But it turned out quite often for me that amount
of work needed for that manual fixing exceeds the amount of work needed to
split file by hand in the first place.
I would not
On Friday, February 23, 2018 at 10:22:55 AM UTC-6, vitalije wrote:
Cleaning generated headlines is just a part of the problem. More serious
> problem is choosing what should go in to single node.
>
I agree completely.
> As far as I am concerned, I would much prefer to have a toolbox with
>
There are problems assigning lines to nodes.
>
> Edward
>
Precisely
--
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 leo-editor+unsubscr...@googlegroups.com.
On Friday, February 23, 2018 at 10:32:59 AM UTC-6, Edward K. Ream wrote:
I am working on improvements [to . Please hold suggestions for a bit.
>
Rev 0deba52 completes the present round of work on this project. There are
no problems that I can see with the *headlines* when importing leovue/src.
On Friday, February 23, 2018 at 9:42:24 AM UTC-6, Edward K. Ream wrote:
> The javascript importer now defines [clean_headline] this way:
I am working on improvements. Please hold suggestions for a bit.
Edward
--
You received this message because you are subscribed to the Google Groups
Cleaning generated headlines is just a part of the problem. More serious
problem is choosing what should go in to single node. As far as I am
concerned, I would much prefer to have a toolbox with several commands to
help me importing files on my own. I wrote about that idea here
Leo's import system has many strengths. The most important is that code
will almost always import correctly even if the resulting nodes aren't even
close to optimal. This is particularly important for javascript, where
coding styles vary so widely.
After generating nodes, the import system
