Submitted by KeithB on 2009/07/15 15:44
I tried converting a lot of MHT files over to HTM in my main database , and ran into a few things that are confusing/and may be bugs:

1) For a locked item--you can still change htm to mht and vice versa.  Is this by design?

2) For an existing item with HTML text (not MHT) --if I click "create a new HTML document" , the html pane text blanks; but the HTML (ID=1608) Using Forms/ /  ... etc text at the top remains.
ItemHTMLText field is still filled, so you can copy it back, but  why does the HTML pane blank without some warning

3)  apparently once I convert MHT's over to HTM, the .MHT files remain--is this by design? 
Am I supposed to go in manually and delete them from a file manager?

Comments

As written in Mantis: http://mantis.sqlnotes.net/view.php?id=755 , I've improved the MHT to HTM conversion. Regarding your questions
  1. This is by design. Lock is only to prevent deleting the item. Changes are permitted on a locked item
  2. My mistake, a confirmation is now shown before erasing the content
  3. By design at the time, because MHT to HTM conversion would lose the images. Now, I've added a check box to delete or not the MHT file
 

jan_rifkinson

2009/07/15 17:31

In reply to by Pierre_Admin

Why would user want to convert from HTML -> MHT?  Or visa-versa for that matter.
 
--
Jan Rifkinson
Ridgefield CT USA
HP Blackbird Vista Ultimate SP-1

KeithB

2009/07/15 21:09

In reply to by jan_rifkinson

[quote=jan_rifkinson]
Why would user want to convert from HTML -> MHT?  Or visa-versa for that matter.
 
--
Jan Rifkinson
Ridgefield CT USA
HP Blackbird Vista Ultimate SP-1
[/quote]
 
Earlier, I liked using Word and the MHT files, but as the built-in html editing has gotten better, I use it for almost everything, except for stuff with pictures.
 
Hence my conversion project (which was bad timing, judging by the description of Mantis 755).
 
I also like the idea of not having a zillion auxiliary files in the .SNDB.files directory.
 
 
 

Armando

2009/07/16 13:58

In reply to by KeithB

>I also like the idea of not having a zillion auxiliary files in the .SNDB.files directory.
 
Having these files outside the database can have its pluses : Desktop Search engines index these quite well. (The main IQbase can be indexed by Archivarius... but not very sexy and easy to read.... Wonder if Windows Desktop Search can indexes these efficiently...)

Tom

2009/07/16 03:43

In reply to by jan_rifkinson

 
an obvious advantage of html is that you dont have to save images locally - so I guess it's whatever you prefer now
With MHT it is presumably easier to go to the IQ folder and copy the file out if you want . .
 

jan_rifkinson

2009/07/16 13:39

In reply to by Tom

Tom, by saving images locally, do you mean on my HD or within the IQ dB? I realize that sounds redundant but one my clog my HD while the other also has the possibility of clogging my dB.
 
--
Jan Rifkinson
Ridgefield CT USA
HP Blackbird Vista Ultimate SP-1

Armando

2009/07/16 13:59

In reply to by jan_rifkinson

>by saving images locally, do you mean on my HD or within the IQ dB?
 
on your HD.

Tom

2009/07/16 16:29

In reply to by Armando

[quote=Armando]
>by saving images locally, do you mean on my HD or within the IQ dB?
 
on your HD.
[/quote]
 
gotta admit I'm getting confused now - MHT files are stored in folder with same name as database
Where are HTML files stored?
And I thought the when saving a web clipping in HTML format that the images were only linked to (i.e. not downloaded at all?)
 
Had a look in the manual & couldnt find any clear description/comparision of both . .

Armando

2009/07/16 17:22

In reply to by Tom

if I'm not mistaken.
 
MHT : imaged saved "locally", text both in DB and folder (option to not keep copy inside the DB)
HTML files : text saved in you DB, images are "linked to" (not downloaded).
 
We should add an explanation in manual...

Pierre_Admin

2009/07/16 20:17

In reply to by Armando

Correct with the following details:
  • MHT converted to HTML now saves images locally
  • In the add new item dialog, I'll add an option to capture web pages to HTML format and save images locally. MHT is best viewed in IE as opposed to HTML which is viewed by all browsers

Armando

2009/07/16 20:50

In reply to by Pierre_Admin

Pierre : So -- considering these changes and the fact MHT is not directly editable in the HTML pane --  in your opinion what will be the advantage of MHT?

Pierre_Admin

2009/07/16 22:55

In reply to by Armando

Single file, sort of like a DOC file (BTW, it should be quite easy for me to edit MHT documents (= expand to temp dir, edit, compact to MHT). When time permits, I'll work on this.
 

jan_rifkinson

2009/07/17 10:11

In reply to by Pierre_Admin

so ultimately, both MHT & HTML will save all data locally. The only difference is that MHT will save all data, i.e. text + images as one file, whereas HTML will separate the images, etc from the text.  Do I have it about right?
 
If so, then it would seem that MHT would be the format where data is less likely to get misplaced. If I were to move an MHT file, I'd be moving everything. If I move an HTML I might have to move more than a single file, ie. perhaps a folder w images, etc.
 
--
Jan Rifkinson
Ridgefield CT USA
HP Blackbird Vista Ultimate SP-1

Pierre_Admin

2009/07/17 10:32

In reply to by jan_rifkinson

This is generally correct. I'd like to add:
  • When you use external storage (i.e. MHT or HTML, as opposed to internal storage, the default if you simply type in the HTML pane), you have the option of storing a copy of the file in your IQBase. If you just move the IQBase without the sub-folders, you'll still be able to view/edit your documents, as these will be recreated when required from the IQBase stored copy. This works fine for MHT (as it is a single file). For external HTML files, you'll be missing images, js, css.
  • Generally, the external storage is called YourIQBase.SNDB.Files. In that folder, you'll find the MHT/HTML files in the format ItemIDXXXX.MHT or .HTM. For each .HTM files, you'll also find a folder named ItemIDXXXX_files that contain all dependant files (images, js, CSS, etc.)