About "remove formatting"

[Notjohn]

If Write will save in *.doc format, you can still try word2cleanhtml dot com online.

[kbanelas]

Hi Doitsu!!
You have told me what I would be afraid..
It's a very simple script that remove all tags of html code except bold, italic, underline and lists.
But now I understand how the plugins work.
Thanks, I will look DiapDealer's Smarten Punctuation plugin.
Regards

edit:

Ei Notjohn!!

Now it's matter of pride.

Create is fantastic, awesome, and the hapiness because of create something that works, it's sublime

Cheers!!

[Doitsu]

Originally Posted by kbanelas

You have told me what I would be afraid..
It's a very simple script that remove all tags of html code except bold, italic, underline and lists.

You don't need a plugin for that, you can clean up a file by using several regular expression searches one after another.

For example:

You could use the following search and replace expressions in a search group:

Find<p[^>]+>
Replace<p>

Replaces all <p class="xx"> with <p>

Find</*span[^>]*>
Replace

Deletes all <span> tags.

For more examples see the Regular Expression thread.

[blackest]

http://www.cssout.com/

might be useful html in and html and separate css file out. Anyone fancy trying it ?

[kbanelas]

Hello guys!!!

Doitsu, I'm sorry but, what you're suggesting, it's a drudgery. I prefer losing my time one day in a little script, that using several regular expressions, all my life.

blackest, I have visited the web link, and it's interesting, but the idea is improvable at least in that web. Perhaps another website works better.

Regards!!

[Doitsu]

Originally Posted by kbanelas

Doitsu, I'm sorry but, what you're suggesting, it's a drudgery. I prefer losing my time one day in a little script, that using several regular expressions, all my life.

Actually, you can use regular expressions in scripts also. They might look rather intimidating at first, but once you learn the basics they can save you hours of manual work.

However, as many other posters have repeatedly suggested, you might save even more time by resaving your original file as a .docx or .odt file and exporting it as a "filtered .html file."

BTW, Calibre can convert a .docx file to a halfway decent epub with very little clutter.

[kbanelas]

Hello!!

I know it's possible I have been an obstinate because of to want doing this plugin but now the work have been made. I'll upload my little script smoothRemove for everybody.
Now in this version of plugin 0.1 you'll be able to realize a complete remove formatting but with the peculiarity of preserve the italics, underline, bold, list and headings tags.
Remember that it's about an special remove formatting. Everything the rest of tags will be removed

ATTENTION: Don't use this plugin with the cover, so if you have one, don't select a complete smoothRemove, only select the files in that you are interested.

See you soon

[KevinH]

Hi,

You seem to either only be working on a set of files without an opf (or that have no entries in the opf).

The calls you make to read and write the files are only correct for files ***not*** part of the manifest in the opf.

        def applySelect(self):

                if self.flagAll.get() == True:
                        for (ID, href) in self.bk.text_iter():
                                html = self.bk.readotherfile(ID)
                                r = Remove(html)
                                html_new = r.get_html()
                                self.bk.writeotherfile(ID,html_new)

If your html files are actually included in the manifest of the opf, the correct way to access these files is via the calls setup to do just that:

    def readfile(self, id):
        # returns the contents of the file with manifest id  (text files are utf-8 encoded)
        return self._w.readfile(id)

    def writefile(self, id, data):
        # writes data to a currently existing file pointed to by the manifest id
        self._w.writefile(id, data)

whereas you used code to read and write files that are **not** part of the manifest.

# reading / writing / adding / deleting other ebook files that DO NOT exist in the opf manifest

    def readotherfile(self, book_href):
        # returns the contents of the file pointed to by the ebook href
        return self._w.readotherfile(book_href)

    def writeotherfile(self, book_href, data):
        # writes data to a currently existing file pointed to by the ebook href
        self._w.writeotherfile(book_href, data)

The ONLY way this would work is that either your opf file is broken or non-existant or not being parsed properly.

So if that code truly works for you, and if the files you edit are actually part of the manifest in the opf, then something is very broken that needs to be fixed. So could you please post just the opf file for a book this code works on so that I can track down why the opf is not being parsed properly and get it fixed in the next release of Sigil.

Thanks,

KevinH

Originally Posted by kbanelas

Hello!!

I know it's possible I have been an obstinate because of to want doing this plugin but now the work have been made. I'll upload my little script smoothRemove for everybody.
Now in this version of plugin 0.1 you'll be able to realize a complete remove formatting but with the peculiarity of preserve the italics, underline, bold, list and headings tags.
Remember that it's about an special remove formatting. Everything the rest of tags will be removed

ATTENTION: Don't use this plugin with the cover, so if you have one, don't select a complete smoothRemove, only select the files in that you are interested.

See you soon

[Doitsu]

Originally Posted by KevinH

The ONLY way this would work is that either your opf file is broken or non-existant or not being parsed properly.

Actually, his plugin works just fine with a regular epub with files manifested in the .opf. I haven't got the faintest idea why, but it does.

@kbanelas: Congratulations on your first working plugin!

[KevinH]

Originally Posted by Doitsu

Actually, his plugin works just fine with a regular epub with files manifested in the .opf. I haven't got the faintest idea why, but it does.

@kbanelas: Congratulations on your first working plugin!

Hi,
Wow! I certainly didn't design it that way. Somehow the manifest ids must be matching the book href, or ... something else is going on. Typically manifest ids do not match hrefs.

I will look into this some more. If you change his calls to use the correct way, does it still work?

KevinH

[kbanelas]

Hi!!

Originally Posted by KevinH

So if that code truly works for you, and if the files you edit are actually part of the manifest in the opf, then something is very broken that needs to be fixed. So could you please post just the opf file for a book this code works on so that I can track down why the opf is not being parsed properly and get it fixed in the next release of Sigil.

Thanks,

KevinH

Thanks to you.

This code works fine with all ebooks that I have. Could the error be other?
I'm at your disposal.

Originally Posted by Doitsu

@kbanelas: Congratulations on your first working plugin!

Thanks, but the plugin works by chance. Or that seems...
This plugin worked fine from the start, so I didn't ask any question.
Anyhow, but not today, tomorrow, I'll look the code again.
Thanks, again
Cheers!!

[KevinH]

Hi,
It will work the way you have it now but it will stop working in the future. The only reason it works now is that I recently changed the code to use a dictionary to map both manifest ids and book hrefs to filepaths. This change allowed bk.writeotherfile and bk.readotherfile to work by accident if you pass in a valid manifest id in place of a href from the book root. The old code did not use this. The upcoming next version code will change this back to the old way of doing things.

So simply just replace your use of bk.writeotherfile with bk.writefile and bk.readotherfile with bk.readfile and then your plugin should continue to work as expected even after the next release of Sigil.

Thanks,

KevinH

[kbanelas]

Hi!
I have fixed the code!!
I think that all is right but please, if you could to look it, I would be thankful.
Cheers!!

[KevinH]

Hi kbanelas,

The use of the edit bookcontainer calls looks exactly right. Very nice job indeed!

Only if you so desire you could simply rename your zip file to include your version information. In other words you could rename smoothRemove.zip to be smoothRemove_v010.zip (no other changes needed ... ie it should still unpack into a smoothRemove folder).

That way if you wanted to change it or add new features in the future, people would not be confused as to which version is newer.

Take care,

KevinH