Resolved Viewing text document with html tags removed

I downloaded a .txt file that must have been a saved version of an html page. I uploaded it here: http://www.paulrittman.com/Translations.txt

The problem is that this is a long book, and the html tags are incredibly awkward to read. I'd like to get a copy of this with the html tags removed. I tried opening it with Kompozer (an html editor), but it wouldn't open it, saying that it wasn't an html file. What should I do, to view this as a normal document, with only the text, and none of the html visible?

Not sure what forum this should be placed in--mods feel free to move it but I'm sure the XP forum regulars can help me out.

 

Hi

a good place to start would be to reinstate the HTML tags "properly" - the angle brackets which start and end the HTML tags have here been replaced with the corresponding "entities "

whether more work is needed after that's been done is hard to determine at the moment because of all the "clutter "

so let's try - gives this

(using global search / replace courtesy of Metapad)

how does that look?

best, HJ

 

Got link to html page. You can right click "save page as html completed" this will allow you to read it offline.

You can highlight and copyNpaste into word.

You can click on the PDF link in the upper left corner and save it as PDF file Choice is yours, Let me know if this works for you.

http://www.bibleviews.com/authority-6.html

 

Thanks. Your language about saving as "save as html completed," which wasn't an option in Google Chrome, led me to open it in IE 8. THat page displayed perfectly, without any of the html tags displayed. This must have been either a bug/idiosyncrasy with Chrome, or at least one of the times when a webpage is either made with MS' html composer (forget the name of that program), or it was simply designed with IE in mind.

At any rate, thanks for the response, as it cued me to the problem--my browser.

 

Hugh, that looks very good. Thanks for your time. That even displays well in Chrome (the font on the title of the section headings at the top was a bit small, but no biggie).

Since you were able to see what was wrong, and fix it---

was this web page poorly designed? Was it something nobody should have done? Or is this the product of using MS FrontPage? I'm wondering why Chrome goofed it up.....

 

I am glad your problem is behind you. Even more pleased that Hugh Jarss ahd coding answer you sought. Any but the simplest Html code is greek to me.

Your most welcome and can you please mark this post as resolved? See: scroll to "mark this post as resolved "

---------------
I believe the original reference and link you used had this document in a format meant for a special reader. See:
http://www.memoware.com/?screen=doc...Greek ~!description^!Greek ~!author^!Greek ~!

Something called a "plucker" ???? For Palm reader.
http://www.memoware.com/?screen=help_format#Plucker

 

nice catch, Ann why oh why didn't I think to look around a bit...

psaulm119 - browser might become more of an issue further down the page, where the page attempts to display various glyphs using symbol font

the page uses quite a lot of special glyphs - I haven't checked them all (am not that clever!), but if you compare this same section rendered in Opera 10.63 Firefox 3.6.11 and IE8, it looks as though using Opera or Firefox might make your life easier than using IE8

...all of which makes me think that going for the PDF would be your safest bet - that way you will stand the best chance of preserving the greek and other letters the way they were intended to look

PDFs can be very good things when special characters get involved

==

umm, yes, the page wasn't written very well (in terms of complying to W3C standards); that wasn't the basic problem which I fixed though, I merely spotted that the < and > characters which should have delineated the HTML tags had (somehow?) become replaced with the corresponding "entities" (which normally get used if a page has to show < or > as part of the text)

but even at that, the "proper" page (at http://www.bibleviews.com/authority-6.html) has 861 errors on it, these errors mean that it won't necessarily work properly, or work the same across different browsers (and many browsers themselves don't conform properly!)

BUT! - there are zillions of pages out there on the internet which are hopeless in terms of complying to the standards; which is why it's far from uncommon to find pages which look "funny ", or different when you look at them with another browser

...so really, it would be a bit unfair to "point the finger" at this page as particularly bad

(and yes! ...pages written with Word (save as HTML) and to a lesser degree other MS software too, do tend to give lots of errors. Microsoft decided to add "3rd party" extensions to the W3C standards which work OK in IE but go wrong in other browsers. W3C just want it all to work for everybody. MS software isn't as bad as it used to be! - pages authored using Word97 were a complete nightmare, for example)

best wishes, HJ

 

indeed, for accuracy, best to stick to using the PDF

hmm, got something wrong there:

...not so, it totally depends upon the particular glyph in question.

Fascinated by the wording: "oxo, translated vinegar "* I looked at how it renders in the various browsers: Opera Firefox IE8 and compared it to the PDF.

In this case, IE8 is clearly doing a lot better than the other two, which show it looking more like a "Chi" than a "Xi ".

[SIZE= "1"]*it just isn't true! Really. Oxo is a stock cube, at least in the UK. Not vinegar. Conclusion: caution advantageous, if using recipes translated from Greek.[/SIZE]

So, psaulm119, the PDF must surely be your most accurate source - none of the browsers get all the glyphs correct. And seriously, for a moment: the results with browsers would be very dependent upon whether the computer has the "Symbol" font installed, and most probably upon the browser's settings for character encoding too.

best wishes, HJ.