Hi Martin,

In my app.cfg there are two lines for kid:
kid.outputformat="xhtml"
kid.encoding="utf-8"

I've tried "xhtml", "xthml-strict" and even "plain" but I allways get
these strange <br></br> (lowercase)-tags :-\
Only if I specify xmlns="http://www.w3c.org/1999/xhtml"; I get
nice-looking <br />-tags but than my py:extend-stuff ignores the
html-code of the master.kid (see first mail)

> How does the Kid file look like?
I have copied the head of my two kid-files in the first mail
(overview.kid and master.kid)... or what kid-file do you mean?!

p.s. I am using kid Version: 0.9.3-1 (according to "apt-cache show
python-kid")

Martin Geisler wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>
> Hi Andreas
>
> > I've tried all possible options but nothing changes. I still get
> > <br> </br> instead of <br /> or I do not get the content from the
> > master.kid... well it was worth a try...
>
> Have you had a look at the kid.outputformat option in app.cfg? It can
> be used to switch between different Kid serializers. They are
> documented here:
>
>   http://kid-templating.org/guide.html#common-output-methods
>
> I believe the default is "html" which gives you uppercase tags and
> empty <BR> elements. Setting it to "xhtml" generates "<br />" tags.
> You shouldn't see "<br> </br>" being output in any case.
>
> How does the Kid file look like?
>
> --
> Martin Geisler  ---  <[EMAIL PROTECTED]>  ---  http://mgeisler.net
>
> Read, write, create Exif data in PHP with PEL:       http://pel.sf.net
> Take control of your webserver with PHP Shell:  http://phpshell.sf.net
>
> --=-=-Content-Type: application/pgp-signature
> X-Google-AttachSize: 189


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to