"W?odzimierz ABX Skiba" <abx### [at] babilonorg <mailto:abx### [at] babilonorg>> wrote in
message <news:hjp39u87rcv46na1l4q7ctfth72qbf0plr@4ax.com>...
> I think it hangs up with <http://www.bmt.com.pl/Poligrodzianie/sigs.pov>

Thank you for testing.
Yes, the on-line version behaves a bit strange for me too, I'm not sure
about what the real limitations are.
But it processed these sigs  for me in two steps ~ 100 lines + the rest.

Gleb

Post a reply to this message

In article <1qp39uklntb84ucah2fs5igj5r1ovvjkri@4ax.com>, abx### [at] babilonorg says...

> Pretty good. My testing file http://www.bmt.com.pl/Poligrodzianie/sigs.pov is
> rather short but it appear with fatal error - execution time too long.

Probably due to that sluggish lycos server. I called it with you file, 
and is now sitting there for more than 9 minutes and has only displayed 
the first 3 sigs until now...

Last night it was very responsive, bot now it takes ages to show 
something at all :-(

> Also
> with some sample css ends of lines are broken.

Wich one? What do you mean with broken? Visible <br> Tags? or something 
different? 
(uhm, does't Windows and Unix use different markers for line-feeds?
Maybe that is the prob, since I only check for \n)

Lutz-Peter

Post a reply to this message

In article <3c91debc@news.povray.org>, gk1### [at] sotonacuk says...

> > The source is in http://mitglied.lycos.de/lpvader/pov2html/p2h.zip
> Have you checked the list of keywords? An item "normal_indices" listed twice
> in docs,

Yep, of course than it's also twice in mine, since I only copy&pasted the 
keywords list from the docs.
But it should't cause a problem, it's just one redundant check for every 
token.

Lutz-Peter

Post a reply to this message

In article <1qp39uklntb84ucah2fs5igj5r1ovvjkri@4ax.com>, abx### [at] babilonorg 
says...

> rather short but it appear with fatal error - execution time too long.

Seems it was't the server alone. I did some profiling and found out that 
for some mysterious reason array_pop() in PHP is extremely slow.

I replaced it with array_walk, and now the whole thing is about 8 times 
faster.

Lutz-Peter

Post a reply to this message

in news:3c9102a2@news.povray.org Gleb wrote:

> [...]
> http://freelocus.com/pov2html.html
> [...] 
> I hope that all keywords are included, but this is a question to test.

It does not deal with nested multiline comments in the right way.
It has problems with a < preceded by a comma (no coloration)
It has sometimes problems with the {}

I tried to make a converter too this weekend, using python. It uses css, 
but it has no file i/o yet, also replacing >,< etc. by proper html esc-
characters is not done yet.
Here's some of its results:
http://members.home.nl/seedseven/povcolor.html

Ingo

Post a reply to this message

On Fri, 15 Mar 2002 21:27:22 +0100, Lutz-Peter Hooge <lpv### [at] gmxde> wrote:
> Wich one?

after you changes it appears in with CSSs

> What do you mean with broken? Visible <br> Tags?

Yes. At begining sigs appear properly from "new of Warp" they seems broken.
Also all sigs are separated with empty line in original file.

Note that pair digit-token ("0translate" for example) isn't highlited
properly. It also isn't highlited in POV-gui but perhaps you can force this
:-)

> (uhm, does't Windows and Unix use different markers for line-feeds?
> Maybe that is the prob, since I only check for \n)

Meybe. For answer you should call 0 800 POV RAY ;-)

ABX

Post a reply to this message

In article <2ubb9uc70mfovpmpgdo5s29p84esaromg9@4ax.com>, abx### [at] babilonorg 
says...

> Yes. At begining sigs appear properly from "new of Warp" they seems broken.
> Also all sigs are separated with empty line in original file.

I can't reproduce this. Maybe it is a bug in your browser (wich one)? 
 
> Note that pair digit-token ("0translate" for example) isn't highlited
> properly. It also isn't highlited in POV-gui but perhaps you can force this
> :-)

I didn't even know the parser accepts such things...

Lutz-Peer

Post a reply to this message

On Mon, 18 Mar 2002 14:52:50 +0100, Lutz-Peter Hooge <lpv### [at] gmxde> wrote:
> > Yes. At begining sigs appear properly from "new of Warp" they seems broken.
> > Also all sigs are separated with empty line in original file.
>
> I can't reproduce this. Maybe it is a bug in your browser (wich one)? 

I'm using IE5. Take a look at urls:
result of your script: http://www.bmt.com.pl/Poligrodzianie/sigs_ie5.png
the same source in POV-Win editor:
http://www.bmt.com.pl/Poligrodzianie/sigs_pov.png

> > Note that pair digit-token ("0translate" for example) isn't highlited
> > properly. It also isn't highlited in POV-gui but perhaps you can force this
> > :-)
>
> I didn't even know the parser accepts such things...

It is unofficial feature for sig writers ;-)

ABX

Post a reply to this message

in news:Xns### [at] povrayorg ingo wrote:

> I tried to make a converter too this weekend, using python. It uses
> css, but it has no file i/o yet, also replacing >,< etc. by proper
> html esc- characters is not done yet.
> 

It all works now:

http://members.home.nl/seedseven/povsdl2html.py

Fancy but probably useless things to add later, some more color-
dictionaries to choose from, optional line numbers, optional links from 
identfiers and macros to the place where they where declared. A project 
mode, feed it the top scene and it will do all associated include files 
and generates appropriate links, maybe even for the standard includes. If 
I feel like it, that is.

Ingo

Post a reply to this message

In article <4psb9ustotrcdg8qj6v0bksk8ceufosdmi@4ax.com>, abx### [at] babilonorg 
says...

> I'm using IE5.
> Take a look at urls:
> result of your script: http://www.bmt.com.pl/Poligrodzianie/sigs_ie5.png

Thanks. It really seems to be a bug in IE, it seems that inside a <pre>-
block it interprets multiple <br> Tags as if there where only one.

> the same source in POV-Win editor:
> http://www.bmt.com.pl/Poligrodzianie/sigs_pov.png

Thats how it should look like, and it does in Netscape and Opera.

I'll find a fix for this (however the HTML and CSS code I used is legal 
according to validator.w3.org).

Lutz-Peter

Post a reply to this message