|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I had another look at the Windows/Linux documentation on what might cause
most of the trouble in Netscape 4 and IE 3 displaying the files.
It seems the major problem are the incorrectly closed tags for anchors and
paragraphs. Here is a corrected example from 'povdoc_003.html' that works
much better with both browsers.
<div class="divh4">
<a name="target_4"></a>
<h4>1.1.2.1 ... And What Is It Not?</h4>
<p>
POV-Ray for Windows is not a modeller. It will not let you design scenes
graphically
on-screen. There are several shareware and freeware programs available for
this purpose. To
write or modify POV-Ray scenes you just edit the actual text file
containing the commands.
</p>
<p>
New users might be surprised to learn that, although this <i>sounds</i>
primitive, it is in
fact one of the things that gives POV-Ray so much power and flexibility.
There are many other
rendering programs that give you a point-and-click interface, but when it
comes down to absolute
control of your scene, it's hard to beat a text-based scene description
language (even though
it's harder for some to learn).
</p>
</div>
The paragraph tags only seem wrong in some of the files, but the anchors
are incomplete throughout the docs, i suppose it won't be that difficult
to modify the script for correcting this.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 02 Jun. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Anyone having looked into this?
If it's too difficult to change for some reason that's ok, but if it's
just a minor change in the script it would be really nice if that could be
fixed.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 14 Jun. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3CFF3DBF.EF6A20F9@gmx.de...
> I had another look at the Windows/Linux documentation on what might cause
> most of the trouble in Netscape 4 and IE 3 displaying the files.
I don't recall seeing the original message you refer to (or even this message,
until I saw your followup).
> It seems the major problem are the incorrectly closed tags for anchors and
> paragraphs. Here is a corrected example from 'povdoc_003.html' that works
> much better with both browsers.
I don't know why this would cause a problem, a missing </p> can always be
inferred and AFAIK this is exactly what browsers do (even old ones).
Nevertheless, I have gone through the windows docs and added any missing ones
(and added opening ones at the start of each section).
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 Jun 2002 22:55:29 +1000, "Chris Cason"
<new### [at] deletethispovrayorg> wrote:
> "Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3CFF3DBF.EF6A20F9@gmx.de...
> > I had another look at the Windows/Linux documentation on what might cause
> > most of the trouble in Netscape 4 and IE 3 displaying the files.
>
> I don't recall seeing the original message you refer to (or even this message,
> until I saw your followup).
So perhaps You also missed my post about lost page of documentation ?
It is still valid for RC6 on win platform.
http://news.povray.org/povray.beta-test/23303/
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
>
> > It seems the major problem are the incorrectly closed tags for anchors and
> > paragraphs. Here is a corrected example from 'povdoc_003.html' that works
> > much better with both browsers.
>
> I don't know why this would cause a problem, a missing </p> can always be
> inferred and AFAIK this is exactly what browsers do (even old ones).
I suppose it's a combination of different effects, it's mainly the
indention what's going wrong, without style sheets everything is fine.
Netscape 4 has some really ugly ways of interpreting things, i guess there
are similar problems with IE3.
> Nevertheless, I have gone through the windows docs and added any missing ones
> (and added opening ones at the start of each section).
Thanks.
Have you also changed the anchors ('<a name="target_4"></a>' instead of
only '<a name="target_4">') these are more important since they occur
throughout the docs.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 14 Jun. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> So perhaps You also missed my post about lost page of documentation ?
No, I saw that, but it's not correct to call it 'lost', and neither is
it correct to say the page has no closed body. It is linked into from
the start page (and has always been), and it is properly closed HTML
insofar as I can tell.
The lack of forward and back links and section numbers is intentional.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3D132BBF.CC6A1707@gmx.de...
> Have you also changed the anchors ('<a name="target_4"></a>' instead of
> only '<a name="target_4">') these are more important since they occur
> throughout the docs.
This causes problems as well ?
I've been using browsers since Mosaic v1.0 and have never noticed an issue
with the lack of a '</a>' for a local target ...
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 Jun 2002 23:59:37 +1000, "Chris Cason"
<new### [at] deletethispovrayorg> wrote:
> "W?odzimierz ABX Skiba" <abx### [at] babilonorg> wrote in message
> > So perhaps You also missed my post about lost page of documentation ?
>
> No, I saw that, but it's not correct to call it 'lost', and neither is
> it correct to say the page has no closed body.
My fault. I didn't rechecked all previous notes but only partially. Currently
there is </body> but I'm pretty sure there wasn't (or there could be a bug in
view source feature in IE).
> It is linked into from
> the start page (and has always been)
Right, I missed this but the reason why I noticed it as 'lost' is becouse
there is no 'next' 'prev' links and no chapter numbering.
> and it is properly closed HTML
> insofar as I can tell.
what about
http://news.povray.org/dvr3au0l9pv2v86amasifb6mlq5t1pja70%404ax.com ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 Jun 2002 16:02:40 +0200, Chris Cason wrote:
> "Christoph Hormann" <chr### [at] gmxde> wrote in message
> news:3D132BBF.CC6A1707@gmx.de...
>> Have you also changed the anchors ('<a name="target_4"></a>' instead of
>> only '<a name="target_4">') these are more important since they occur
>> throughout the docs.
>
> This causes problems as well ?
>
> I've been using browsers since Mosaic v1.0 and have never noticed an
> issue with the lack of a '</a>' for a local target ...
I recommend that you use a tool such as HTML Tidy to check if there
are some errors in the HTML pages. This is a very small tool that can
be used to quickly check the syntax of the pages. Some parts of it
have been included into several HTML editors, but I use it mostly as a
standalone program (use it like this: "tidy -e somepage.html" to show
only the errors).
You can get the latest version of HTML Tidy for several platforms from:
http://tidy.sourceforge.net/
You can also find a link to it from the home page of the World Wide Web
Consortium: http://www.w3.org/
--
http://www.gamers.org/~quinet/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
>
> [...]
>
> This causes problems as well ?
>
> I've been using browsers since Mosaic v1.0 and have never noticed an issue
> with the lack of a '</a>' for a local target ...
As said it seems to be related to incorrect interpretation of the
indention (<div> and 'margin-left') I was astonished about this myself,
but if such a small change helps fixing most problems with two older
browsers...
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 14 Jun. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |