-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have some PT skins I'm using to generate XML responses and am getting
some strange behaviour. I'm not sure if its because I misunderstand
something, there are bugs, or the API could be made more useful.
I will focus this discussion around the
Bernd Dorn wrote:
When I do .po files with the same domain, e.g: Domain: CMS\n and
they have different Language-Code: header e.g: Language-Code: pl\n
and Language-Code: en\n Zope chooses language based on web browser
settings :(. When I'm setting xml:lang and lang attributtes it
doesen't make
Alan Milligan [EMAIL PROTECTED] wrote:
I have some PT skins I'm using to generate XML responses and am getting
some strange behaviour. I'm not sure if its because I misunderstand
something, there are bugs, or the API could be made more useful.
I will focus this discussion around the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
|
| ZPT will process tal instructions in XML templates only if the proper
| namespace is declared. You must have:
|
| xmlns:tal=http://xml.zope.org/namespaces/tal;
|
Ok, I've explicitly included this now as well, and it
Alan Milligan wrote:
| ZPT will process tal instructions in XML templates only if the proper
| namespace is declared. You must have:
|
| xmlns:tal=http://xml.zope.org/namespaces/tal;
|
Ok, I've explicitly included this now as well, and it behaves properly :)
What is the rationale for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
| | Use:
| |
| | [default]
| | content_type = text/foobar
|
| No, this doesn't work either :(
|
|
| Well it should, there are unit tests in CMFCore that explicitely test
| this kind of .metadata file.
|
No, I had a look and
Alan Milligan wrote:
Florent Guillaume wrote:
| | Use:
| |
| | [default]
| | content_type = text/foobar
|
| No, this doesn't work either :(
|
|
| Well it should, there are unit tests in CMFCore that explicitely test
| this kind of .metadata file.
|
No, I had a look and there's a strange test with
