Shailesh Kumar wrote:
Thanx for the hint. I still don't know how to programmatically access the
event log. will try to figure it out.
Why do you need to know programmatically?
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Hi David,
I found another workaround. I defined a dummy Widget for the
abstract Field-field. Something like this:
from zope.app.form.browser.widget import SimpleInputWidget
class DummyWidget(SimpleInputWidget):
def __call__(self):
pass
and additional in zcml:
Although it'
I have 2 different zope applications running (on different machines) and
they would be talking to each other, one is a master application and there
may be multiple instances of the other one (on different machines). I need
the port number information for registing one with another programmatically
Rupert Redington schrieb:
[..]
I'm constantly aware that I need a much better grasp of character
encoding issues (and had hoped that the wonders of unicode/UTF-8 would
save me from this) - can anyone give me a pointer?
Well, there are the "officials" like:
http://unicode.org
http://
Raphael Ritz wrote:
> Well, there are the "officials" like:
>
> http://unicode.org
> http://en.wikipedia.org/wiki/Unicode
>
> but you want probably something more like
>
> http://www.joelonsoftware.com/articles/Unicode.html
>
> and for Python in particular I found
>
> http://w
Hello Rupert,
I'm not a mail+RFC expert, but I would try to pass the content
encoded as UTF-8 and set the headers accordingly.
Wednesday, November 29, 2006, 1:28:41 PM, you wrote:
RR> Raphael Ritz wrote:
>> Well, there are the "officials" like:
>>
>> http://unicode.org
>> http://en.wiki
On 11/29/06, Rupert Redington <[EMAIL PROTECTED]> wrote:
Those are great pointers, thanks, but I still can't understand why
zope.app.mail's MailDir functions want to encode the message using the
'ascii' encoding, nor does there seem to be any way to suggest a
different encoding to the mail system
Rupert Redington schrieb:
[..]
How is it possible to send emails containing non-ascii encodings from
zope? Is there a problem with the python smtplib which is forcing this
behaviour? (Or do I still not get it...?)
[I guess the latter ... :-) ]
Well, I only responsed to the 'pointer to Unicod
Martijn Pieters schrieb:
On 11/29/06, Rupert Redington
<[EMAIL PROTECTED]> wrote:
Those are great pointers, thanks, but I still can't understand why
zope.app.mail's MailDir functions want to encode the message using the
'ascii' encoding, nor does there seem to be any way to suggest a
different e
On 11/29/06, Raphael Ritz <[EMAIL PROTECTED]> wrote:
The mail's body or pay load on the other hand can have
any encoding.
Nonsense. From RFC 2822, section 2.1:
At the most basic level, a message is a series of characters. A
message that is conformant with this standard is comprised of
c
Martijn Pieters schrieb:
On 11/29/06, Raphael Ritz
<[EMAIL PROTECTED]> wrote:
The mail's body or pay load on the other hand can have
any encoding.
Nonsense. From RFC 2822, section 2.1:
At the most basic level, a message is a series of characters. A
message that is conformant with this st
Hi,
in a formlib based form I would like to have more control over the
rendering of the widgets.
is it possible to call widget with a specific name directly instead of
running through all on a repeat loop?
for example
I saw that there is a get method but I can't access it form the page
te
I am creating a custom content container and am getting the intricacies of
the addform browser zcml directive. When I add an object in the ZMI to my
custom container I notice that the __setitem__() method is called after I
hit "Add" button. I also see how the set_before_add and set_after_add
opti
Hi,
On Wed, Nov 29, 2006 at 06:37:53PM +0100, Dennis Schulz wrote:
> Hi,
>
> in a formlib based form I would like to have more control over the rendering
> of the widgets.
> is it possible to call widget with a specific name directly instead of
> running through all on a repeat
> loop?
> for e
14 matches
Mail list logo