POV-Ray : Newsgroups : povray.beta-test : More minor, minor doc issues Server Time
4 Nov 2024 17:31:36 EST (-0500)
  More minor, minor doc issues (Message 1 to 10 of 15)  
Goto Latest 10 Messages Next 5 Messages >>>
From: Anders K 
Subject: More minor, minor doc issues
Date: 17 Sep 2001 11:29:34
Message: <3ba616de$1@news.povray.org>
These are just a few minor things I've noticed when looking through the docs
(beta 2).


In the index tab:
Lots of the index links take me just below a section heading. For
example, the first entry in the index, "#break". Shouldn't they take
me just above the section heading instead?

When I double-click on most of the index items, the "Locate",
"Previous", and "Next" buttons become disabled, which is slightly
annoying.

Lots of the index entries are redundant (for example, "#default" and
"#default directive"). I suppose this doesn't really matter though;
better too many than too few! :-)


In source from HTML pages:
> </head>
> <a name="target_nnnn">
> </head><body bgcolor="#ffffff">
  ^^^^^^^
The </head> tag appears to be duplicated in every HTML page. (I know,
it's none of my business. :-))


In Section 6.0, "Scene Description Language":
> For details on those five items see section "Language Directives",
> section "Objects",
           ^^^^^^^
The link here only includes Object and not the s, and the link points
to "References to 'object'", instead of section 6.5 as it should.


In Section 7.13.4, "shapesq.inc":
> Bicorn
>     [...]
>     y^2 - (x^2 + z^2) y^2 - (x^2 + z^2 + 2 y - 1)^2 =

Equals what? :-)

> Torus_40_12 Torus having major radius sqrt(40), minor radius
> sqrt(12).

Should be two seperate lines to be consistent.

> Sinsurf
>     [...] For best results, scale by something like <1 1 0.2>.

Should probably be <1, 1, 0.2>.


In Section 7.18.3, "Woods:" (the colons from these section titles
probably shouldn't be here, for consistency):
> Dark_Wood
>     Dark wood with a,ish hue to it.

Huh? :-)


MISSING HTML LINKS
In these cases, the text pointed to should probably be a link, but
isn't.

In Section 1.5, "Using the Internal Editor":
> (CodeMax from WinMain software - http://www.winmain.com/)
                                   ^^^^^^^^^^^^^^^^^^^^^^^
In Section 1.11.8, "Bug Reporting via our News Server"
> See http://www.povray.org/groups.html for information about [...]
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In Section 8.2.1, "Contacting the authors":
> [...] via the internet at http://www.povray.org/.
                            ^^^^^^^^^^^^^^^^^^^^^^
In Section 8.3.1.3, "Apple  Macintosh" (the section title appears to
contain a double space):
> Apple's web site <http://developer.apple.com/sdk/>
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In Section 8.3.2.1, "World Wide Website www.povray.org"
> For more information about the server see
> http://www.povray.org/groups.html.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In Section 8.3.2.2, "Books, Magazines and CD-ROMs"
> You can always find the latest information on what is available at
> our web site www.povray.org.
               ^^^^^^^^^^^^^^


PRESENT TENSE REFERENCES TO EARLIER VERSIONS

In Section 3.4.13, Text Object:
> Now, for POV-Ray 3.0, a new primitive has been introduced that can
> use any TrueType font to create text objects.

In Section 6.1.3.2, "Float Identifiers", Section 6.1.4.2, "Vector
Identifiers", and Section 6.1.5.3, "Color Identifiers":
> This semi-colon is new with POV-Ray version 3.1.

In Section 6.2.2.1, "Declaring identifiers" (should this be
capitalized?), and Section 6.2.5, "The #version Directive":
> This semi-colon is introduced in POV-Ray version 3.1.

In Section 6.2.6, "Conditional Directives":
> POV-Ray 3.0 allows a variety of new language directives to
> implement conditional parsing [...]

In Section 6.5, "Objects":
> The "Interior" is a feature introduced in POV-Ray 3.1.

In Section 6.6, "Interior":
> Introduced in POV-Ray 3.1 is an object modifier statement called
> interior.

In Section 6.11.3.2, "Image File Gamma":
> The new PNG format files generated by POV-Ray 3.0 overcome the
> problem of too much or not enough gamma correction [...]

Anders


Post a reply to this message

From: Adrien Beau
Subject: Re: More minor, minor doc issues
Date: 17 Sep 2001 11:57:24
Message: <3BA61D63.5C77DA3F@sycomore.fr>
Hey, this one isn't so "minor, minor". I'd even it's the
biggest to date.

-- 
Adrien Beau - adr### [at] freefr - http://adrien.beau.free.fr
 Mes propos n'engagent que moi et en aucun cas mes employeurs


Post a reply to this message

From: ingo
Subject: Re: More minor, minor doc issues
Date: 17 Sep 2001 16:26:02
Message: <Xns911FE43554A2Eseed7@povray.org>
in news:3ba616de$1@news.povray.org Anders K. wrote:

> In the index tab:
> Lots of the index links take me just below a section heading. For
> example, the first entry in the index, "#break". Shouldn't they take
> me just above the section heading instead?
> 

General rule I try to follow, if the link is pointing to a title or a 
group of "linkto's" near a title, as in the #break example, the jump 
will be made to a position below the title. The reason for this is that 
I "don't know" where a page break will be placed by the doc-generation 
scripts. Currently it is at a <h3> title for the windows docs, but this 
has been different in pre-beta versions. Don't know what it is for the 
mac version, nor what it can or will be in the future.

For all other items I'll see what I can do.

Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/


Post a reply to this message

From: Chris Cason
Subject: Re: More minor, minor doc issues
Date: 18 Sep 2001 12:00:43
Message: <3ba76fab@news.povray.org>
> Lots of the index links take me just below a section heading. For
> example, the first entry in the index, "#break". Shouldn't they take
> me just above the section heading instead?

Do you have ActiveX disabled ?

-- Chris


Post a reply to this message

From: Anders K 
Subject: Re: More minor, minor doc issues
Date: 18 Sep 2001 17:25:49
Message: <3ba7bbdd$1@news.povray.org>
> > Lots of the index links take me just below a section heading. For
> > example, the first entry in the index, "#break". Shouldn't they take
> > me just above the section heading instead?
>
> Do you have ActiveX disabled ?

No, but why would ActiveX change the place in the page that the links point
to?

Anders


Post a reply to this message

From: Chris Cason
Subject: Re: More minor, minor doc issues
Date: 18 Sep 2001 22:11:23
Message: <3ba7fecb@news.povray.org>
"Anders K." <and### [at] f2scom> wrote in message news:3ba7bbdd$1@news.povray.org...
> No, but why would ActiveX change the place in the page that the links point
> to?

HTML Help uses an ActiveX control in the index pane, and the symptom of having
it disabled (at least for one pre-beta tester) was exactly as you described.
Entries would take you to the top of a page but never to a point within it.

What is your version of IE ?

-- Chris


Post a reply to this message

From: Anders K 
Subject: Re: More minor, minor doc issues
Date: 19 Sep 2001 08:39:58
Message: <3ba8921e$1@news.povray.org>
> HTML Help uses an ActiveX control in the index pane, and the symptom of
having
> it disabled (at least for one pre-beta tester) was exactly as you
described.
> Entries would take you to the top of a page but never to a point within
it.

Oh; that's not exactly what I was saying. For example, with #break in the
index, the link currently points to position [B] below; I think it should
point to position [A] so you can see the heading.

  [A] 6.2.6.3  The #switch, #case, #range and #break Directives

  [B] A more powerful conditional is the #switch directive. The syntax is as
follows...

But I guess Ingo has a reason for pointing it to [B]. That's fine; it
doesn't really matter that much.

> What is your version of IE ?

IE 6.0, HTML Help 1.3.

Anders


Post a reply to this message

From: Chris Cason
Subject: Re: More minor, minor doc issues
Date: 19 Sep 2001 09:27:08
Message: <3ba89d2c@news.povray.org>
> Oh; that's not exactly what I was saying. For example, with #break in the
> index, the link currently points to position [B] below; I think it should
> point to position [A] so you can see the heading.

This is just the way the doc generator works. I'd like to change it but it's
not trivial. I'll see what I can do.

-- Chris


Post a reply to this message

From: Glen Berry
Subject: Re: More minor, minor doc issues
Date: 20 Sep 2001 00:00:41
Message: <SF+pO+3qPmm8ydgkqlqFaoeQDhih@4ax.com>
On Tue, 18 Sep 2001 17:26:03 -0400, "Anders K." <and### [at] f2scom>
wrote:

>> > Lots of the index links take me just below a section heading. For
>> > example, the first entry in the index, "#break". Shouldn't they take
>> > me just above the section heading instead?
>>
>> Do you have ActiveX disabled ?
>
>No, but why would ActiveX change the place in the page that the links point
>to?

I get the same sort of behaviour. The index link for "pi" is even
worse. It seems to make no difference whether I enable ActiveX or not.

I must admit that until I installed POV 3.5, I didn't use Internet
Exploder for anything, and I only installed IE5 to have access to the
POV help files. I saw several settings in the "Internet Security"
menus that affected ActiveX. I tried changing all of them, and I
couldn't change the behaviour of POV's help system. I suppose it's
possible that I didn't change the proper setting in some menu,
somewhere, but I doubt it.

<The following is margainly on topic for this thread, but I felt it
needed to be said.>

For what it's worth, I really don't like having POV-Ray rely on
Internet Explorer at all. My computer and I lived very happily without
IE5, and had intended to do so for the rest of eternity - until POV
3.5 for Windows came out, at least. 

It's almost as bad as when I recently tried to update Norton
Anti-Virus and it wanted me to install some sort of Windows Scripting
(or something like that), just so Norton Anti-Virus could protect me
from it! Now I can't upgrade my virus checker any more, without adding
this additional Microsoft "junk" software to my system, which I'll
never use, only so Norton can try its best to protect me from it.

Overall, The POV-Team has done an excellent job with POV-Ray for
Windows 3.5, and I certainly appreciate their efforts. I just wanted
to be on record as not appreciating this particular aspect of the
POV-Ray help implementation.


Thanks for reading,
Glen


Post a reply to this message

From: Anders K 
Subject: Re: More minor, minor doc issues
Date: 20 Sep 2001 08:36:20
Message: <3ba9e2c4$1@news.povray.org>
> I get the same sort of behaviour. The index link for "pi" is even
> worse. It seems to make no difference whether I enable ActiveX or not.

I don't think this is really a bug. In the case if pi, I think it would be
better if the link pointed to 6.1.3.4.1, Constant Identifiers, so that you
can see the whole definition of pi, not just what it's used for. But it
really doesn't matter that much.


Post a reply to this message

Goto Latest 10 Messages Next 5 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.