Forum Posts Feed
Structured Document Editors?
< Next Topic | Back to topic list | Previous Topic >
Posted by Dave Ewins
Jul 19, 2010 at 12:48 PM
Sense Version 1.7.0 has been released today http://www.silvaelm.com/download.shtml
This fixes a number of issues including RTF and Text file Import for the Personal Version.
I’d be interested in the bug details in Sense so they can be fixed?
Dave Ewins
Posted by Derek Cornish
Jul 20, 2010 at 03:49 AM
Lucas,
Looks as though the developer has now put additional import and export features into the “Personal” edition (see his post on Sense v1.70 today. Good show!
Has anybody experimented with importing Brainstorm text files into Sense? This would seem to me to be one obvious use for Sense - i.e. start with a detailed outline and then move this into Sense for further drafting.
Derek
Posted by Dave Ewins
Jul 21, 2010 at 08:26 AM
Hi
Although Sense should import the BrainStorm Outline text file sucessfully, the resulting format isn’t structured being simply a flat document of paragraphs.
A more rewarding approach is via Sense To Webpage (A maintenance version is available as detailed later) - Sense To Webpage will hopefully convert your BrianStorm Html file to a Sense Document..
The procedure to try is as follows:
Publish your BrainStorm file as as a simple outline version (FullJavaScript model is switched off).
Run Sense To Webpage and open a New “Project by local file open” selecting the html file.
The Validation should initially fail with a “doctype” as an unexpected token.
Close this dialog and allow a XHTML Resolver Retry by selecting Yes.
If the Validation is now successful, Click any of the links in the Navigator browser view to open Sense and the content should hopefully now be structured into sections.
It’s important to Save As your file somewhere useful for later use.
Exit Sense and Exit Sense To Webpage not saving (cancelling) the project to tidy up.
I have placed on the support site http://support.silvaelm.com/maintenance/tools/ a Sense To Webpage development version (1.4.1) incorporating extra handling to convert HTML 4 (transitional) to XHTML.
Dave Ewins
Posted by Derek Cornish
Jul 21, 2010 at 04:57 PM
Hi Dave,
Yes, this looks like a very viable solution. I have a Brainstorm outline file that I’m working on with a colleague. Just as an experiment I downloaded the Sense to Webpage program and loaded the exported html file (simple outline version) from BS into it.
Everything worked well until the XHTML Resolver got to work on tidying up the file, when it threw up the following error message:
“Error: CreatWebpageOutline
Information:
Outlining Webpage
Outlining Webpage
Invalid character in the given encoding. Line 35, position 1029.”
At this point the Resolver stopped and the view of my html file was replaced by the Welcome page - presumably because the Resolver could not proceed any further.
When I later looked at this line and position in the Brainstorm html file, using a syntax editor (http://www.econtrol.ru) with word wrap off, I couldn’t see anything obviously wrong. This position was at a word in the middle of a sentence that began and ended with “  ”. The sentence itself was embedded in a longer paragraph. I also checked with another editor (HippoEDIT) and got the same result.
What should I try next?
Derek
Posted by Dave Ewins
Jul 21, 2010 at 07:18 PM
Hi Derek,
Good work.
Interestingly, the XHTML Resolver / Validation has passed—- the failure
in the Outlining Webpage suggests the presence of a special character
encoding in the html like ® that isn’t being handled by the subsequent XSL transform - it may be that this is in a meta element within the html head or attribute somewhere—
special characters are handled in the main body text nodes.
The Sense To Webpage Help provides a listing of Special Characters currently supported.. Also
there is an Invalid Character Errors explanation within the Validation Errors help page.
Please check for a special character encoding around line 35 where a sub-string starts with an ampersand and ends with a semicolon— it may be that it’s an encoding that isn’t supported currently.
If there is a special character encoding, in what context is it occuring—ie html tag, attribute etc?
It would help greatly if you could send me even a snippet of the file around
line 35—unfortunately, it isn’t necessarily easy to strictly identify the
exact location of the error despite the error reporting from the underlying
system.
Dave