Gerald Richter wrote:
Well, now I see it works when I write [$ syntax + ParkhotelPruhonice $] <h2>Parkhotel Průhonice</h2> It's working now, I must have done something stupid... I'm sorry. - Robert PS1 Actually I tried [- Execute({inputfile => '*', syntax => 'Embperl ParkhotelPruhonice'}) -]
but now I have the correct one[- Execute({inputfile => '*', syntax => 'EmbperlNoTR ParkhotelPruhonice'}) -]
I don't put </tr> elements into HTML and Embperl used to complain
so I have my own sytax without automatic table processing. I can guess
Embperl didn't find </tr> in the source and instead of returning
an error returned some wierd output - it behaves this way at times...PS2 When I'm at it: <td> doesn't have to be closed and Embperl respects it and according to the HTML specs TR doesn't have to be closed too - can default Embperl be made more forgiving and ignore unclosed TR's? My hack just remove <tr> processing completely, that is hardly optimal |
- Re: Redefining common tags? (partial solution) RobertCZ
- RE: Redefining common tags? (partial solution) Gerald Richter
- Re: Redefining common tags? (partial solution) RobertCZ
- RE: Redefining common tags? (partial solution) Gerald Richter
- Re: Redefining common tags? (partial solut... RobertCZ
- RE: Redefining common tags? (partial ... Gerald Richter
- Re: Redefining common tags? (part... RobertCZ
- RE: Redefining common tags? (part... Gerald Richter
- Re: Redefining common tags? (part... RobertCZ
- RE: Redefining common tags? (part... Gerald Richter
- Re: Redefining common tags? (part... RobertCZ
- RE: Redefining common tags? (part... Gerald Richter
- Re: Redefining common tags? (part... RobertCZ
- RE: Redefining common tags? (part... Gerald Richter
