Re: Announcing the book on the website

[<pl...@pi...>]

On Mon, 24 Mar 2008 06:48:27 +0100, Philipp K. Janert <ja...@ie...>  
wrote:

>
> Alright. I'll try again.
>
> On Sunday 23 March 2008 21:32, you wrote:
>> On Sunday 23 March 2008 19:43, Philipp K. Janert wrote:
>> > Ok, here is another attempt, based on Ralf's
>> > comment.
>> >
>> > 	http://philipp-janert.com/gnuplot/www/index4.html
>> >
>> > At least on my screen, this does not wrap.
>>
>> It does on mine.
>>


3. Woking With Data

LOL, is that how the chinese cook thier results ?


Seriously, I agree two graphics is a bit much. I'd suggest dropping the 2D  
since the other shows the full abilities of gnuplot.

The whole upper section is too big in my view, about 2/3 of my browser  
window. You could let the menu start at top left (classic position) , this  
would reduce the overall height.

The H1 is wrapping here and a quick look at sourse shows several typos  
that are probably causing irregular results as different browsers try to  
guess how it should render the faults.

It seems , like me , you like to do your html by hand but the human eye is  
not the most efficient parser for checking typos.

You could use a syntax aware editor (I use kdevelop or bluefish for html)  
of check out the online verification tools of w3c.  
http://validator.w3.org/check#

>> This page is not Valid -//w3c//dtd html 4.0  
>> transitional//en!Result:	Failed validation, 18 Errors

If you use Opera it has a rightclick option that submits the current page  
to this checker in one click, it gives you exact info on each error. HTH.



In general , I agree with others that the TOC is a bit out of place here.  
The book is a great asset to gnuplot but probably should remain a minor  
part of the homepage. I also don't understand why the link Gnuplot in  
Action links back to the same page. This should go to the homepage of the  
book where stuff like TOC can be seen in detail.

I find the main text is getting a bit too small. It's getting to the point  
where the font rendering is getting a somewhat distorted. Again this may  
be the result of errors in the markup.

regards, Peter.