From duncan.booth at suttoncourtenay.org.uk  Thu Feb  1 17:19:46 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Thu, 1 Feb 2007 16:19:46 +0000 (UTC)
Subject: [kupu-dev] deleting tables - small proposal
References: <epnbgg$fvp$1@sea.gmane.org>
	<Xns98C96D00E59duncanrcpcouk@127.0.0.1>
	<epq0io$had$1@sea.gmane.org>
Message-ID: <Xns98CA9A5C52453duncanrcpcouk@127.0.0.1>

yuppie <y.2007- at wcm-solutions.de> wrote:


> AFAICS these buttons exist already. Something wrong with them?
> 
No. My confusion,


From duncan.booth at suttoncourtenay.org.uk  Thu Feb  1 17:19:46 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Thu, 1 Feb 2007 16:19:46 +0000 (UTC)
Subject: [kupu-dev] br question
References: <45BFB27B.2030806@accessibiliteweb.com>
	<Xns98C8D8AC4B532duncanrcpcouk@127.0.0.1>
	<45C097C7.2070006@accessibiliteweb.com>
Message-ID: <Xns98CA8925CDC18duncanrcpcouk@127.0.0.1>

Christophe B?langer <cbelanger at accessibiliteweb.com> wrote:

> Thank you very much. You see it right ... i'm using Plone (without html 
> tidy). So everythings works fine. Kupu is a great tool for our needs, we 
> need a WYSIWYG that can be very restrictive to keep the accessibility 
> level that we target (AA).
> 
> In this way, where can I replace the actual tags behind the ?B? and ?I? 
> button ? I need to put ?strong? and ?em? instead.
> 

I think kupu 1.4 already does that.

When it loads into Firefox it replaces strong/em with b/i because Firefox 
doesn't let you edit strong/em. IE edits either strong/em or b/i but always 
generates strong/em. When saving any b/i tags are replaced by strong/em.



From g.bernhard at akbild.ac.at  Tue Feb  6 15:58:32 2007
From: g.bernhard at akbild.ac.at (bernhard)
Date: Tue, 6 Feb 2007 15:58:32 +0100
Subject: [kupu-dev] image upload
Message-ID: <FAAC01AA-1B17-4233-9981-3B30579F51D6@akbild.ac.at>

Hi Kupu dev list!!

if we upload an image in kupu with the image button / panel there is  
no way to upload an image and then set its size etc in plone - one  
has to click OKAY and the re-enter the same panel again is there  
another way? Can we make a button that just says 'UPLOAD NOW' so we  
can avoid that users have to get in and out of the panel every time?  
It is anoying to re-open the same panel for every upload;

i see kupu improve and improve, so thanks everyone for the good work  
that has been done!!!

Georg Gogo. BERNHARD
g.bernhard at akbild.ac.at

From florian.schulze at gmx.net  Wed Feb  7 13:02:19 2007
From: florian.schulze at gmx.net (Florian Schulze)
Date: Wed, 07 Feb 2007 13:02:19 +0100
Subject: [kupu-dev] Release tag for kupu 1.3.9 missing
Message-ID: <op.tndnp5buhjnvn3@news.gmane.org>

Hi!

Again there is a release of kupu without a tag. Who does the releases?

Regards,
Florian Schulze


From g.bernhard at akbild.ac.at  Thu Feb  8 10:39:33 2007
From: g.bernhard at akbild.ac.at (bernhard)
Date: Thu, 8 Feb 2007 10:39:33 +0100
Subject: [kupu-dev] nbsp tags disappear, breakin' paragraphs
Message-ID: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>

hello again, kupu list!

i have another problem with kupu - i have made a button that inserts  
an image into the dom tree usinng javascript. the html code that i  
insert contains [&nbsp], because otherwise some elements of the code  
are not selectable on clicks. when i click 'HTML' or save all the  
[&nbsp] tags are being removed.

my question now is:
how can i prevent kupu from removing all the [&nbsp] tags?

this issue is pretty urgent for us, so please help me find the right  
solution!

another issue is that kupu seems to insert [p][br /][/p] sometimes  
when return is pressed; can i prevent this, too?

thx for help, Gogo.

From duncan.booth at suttoncourtenay.org.uk  Fri Feb  9 11:31:33 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Fri, 9 Feb 2007 10:31:33 +0000 (UTC)
Subject: [kupu-dev] nbsp tags disappear, breakin' paragraphs
References: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>
Message-ID: <Xns98D1AA749E088duncanrcpcouk@127.0.0.1>

bernhard <g.bernhard at akbild.ac.at> wrote:

> hello again, kupu list!
> 
> i have another problem with kupu - i have made a button that inserts  
> an image into the dom tree usinng javascript. the html code that i  
> insert contains [&nbsp], because otherwise some elements of the code  
> are not selectable on clicks. when i click 'HTML' or save all the  
> [&nbsp] tags are being removed.

Interesting. It seems that non-breaking spaces are being lost when you use 
the HTML source view. If you enter &nbsp; in source view, go back to the 
wysiwyg view, and save the document then you still have a non-breaking 
space (although it is no longer stored as an entity escape so you have to 
examine a character dump to verify that this is the case).

I guess there's a bug somewhere. Probably I need to entity escape the 
source view which is a pity as I can't entity escape the text that Kupu 
saves because Plone has (or had? I haven't checked recently) buggy full-
text indexing which didn't understand html entities.

> another issue is that kupu seems to insert [p][br /][/p] sometimes  
> when return is pressed; can i prevent this, too?

Firefox? If you figure out a way to prevent Firefox inserting strange 
things when you hit return then I'll buy you several beers.


From g.bernhard at akbild.ac.at  Fri Feb  9 12:09:42 2007
From: g.bernhard at akbild.ac.at (bernhard)
Date: Fri, 9 Feb 2007 12:09:42 +0100
Subject: [kupu-dev] nbsp tags disappear, breakin' paragraphs
In-Reply-To: <Xns98D1AA749E088duncanrcpcouk@127.0.0.1>
References: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>
	<Xns98D1AA749E088duncanrcpcouk@127.0.0.1>
Message-ID: <1606606C-B498-408E-9C9C-2191909AEE21@akbild.ac.at>

On 09.02.2007, at 11:31, Duncan Booth wrote:

> bernhard <g.bernhard at akbild.ac.at> wrote:
>
>> hello again, kupu list!
>>
>> i have another problem with kupu - i have made a button that inserts
>> an image into the dom tree usinng javascript. the html code that i
>> insert contains [&nbsp], because otherwise some elements of the code
>> are not selectable on clicks. when i click 'HTML' or save all the
>> [&nbsp] tags are being removed.
>
> Interesting. It seems that non-breaking spaces are being lost when  
> you use
> the HTML source view. If you enter &nbsp; in source view, go back  
> to the
> wysiwyg view, and save the document then you still have a non-breaking
> space (although it is no longer stored as an entity escape so you  
> have to
> examine a character dump to verify that this is the case).

Entering &nbsp; in html view and switching back to 'normal' kupu view  
i found no &nbsp; any more; I looked into the dom using Firebug - no  
&nbsp;
The only suspicious line i found in kupu code is:
kupuploneeditor.js #103
'''
     if (/^<body[^>]*>(<\/?(p|br)[^>]*>|\&nbsp;)*<\/body>$/.test 
(contents)) {
         contents = ''; /* Ignore nearly empty contents */
     }
'''

> I guess there's a bug somewhere. Probably I need to entity escape the
> source view which is a pity as I can't entity escape the text that  
> Kupu
> saves because Plone has (or had? I haven't checked recently) buggy  
> full-
> text indexing which didn't understand html entities.

If you want to have a serious i18n aware catalog you will have to use  
TextIndexNG - and TextIndexNG knows how to deal with html entities  
(hopefully); I would like to know if it is hard to locate the code  
where the entities are dropped - is it zope, plone or kupu? As long  
as it is not Python we definitively can handle :-P  People are unable  
to edit the image modules i put in otherwise.

>> another issue is that kupu seems to insert [p][br /][/p] sometimes
>> when return is pressed; can i prevent this, too?
>
> Firefox? If you figure out a way to prevent Firefox inserting strange
> things when you hit return then I'll buy you several beers.

If you can make &nbsp; persistent I owe YOU one ;-)

Let's find that.
Gogo.




From florian.schulze at gmx.net  Sat Feb 10 16:02:57 2007
From: florian.schulze at gmx.net (Florian Schulze)
Date: Sat, 10 Feb 2007 16:02:57 +0100
Subject: [kupu-dev] Release tag for kupu 1.3.9 missing
References: <op.tndnp5buhjnvn3@news.gmane.org>
Message-ID: <op.tnjf271ihjnvn3@news.gmane.org>

On Wed, 07 Feb 2007 13:02:19 +0100, Florian Schulze  
<florian.schulze at gmx.net> wrote:

> Hi!
>
> Again there is a release of kupu without a tag. Who does the releases?
>
> Regards,
> Florian Schulze


Thanks for adding the tag.

Regards,
Florian Schulze


From y.2007- at wcm-solutions.de  Sun Feb 11 21:35:08 2007
From: y.2007- at wcm-solutions.de (yuppie)
Date: Sun, 11 Feb 2007 21:35:08 +0100
Subject: [kupu-dev] Kupu form field
Message-ID: <eqnupu$irt$1@sea.gmane.org>

Hi!


By default Kupu is a 'document-centric' editor. But - as the Plone 
integration demonstrates - Kupu can also be used as form field.

In 'common' there are kupuinit_form.js and kupuform.html. But this 
sample implementation is still 'document-centric' - it just uses a form 
for submitting changes.

I'd like to have a sample implementation in 'common' that behaves more 
like the Plone integration. A lot of work has been done for Plone that 
seems to be generally useful. A sample implementation could make more 
obvious which code is generally useful and how to use it outside Plone. 
Instead of adding a new sample implementation, I propose to modify 
kupuinit_form.js and kupuform.html for this purpose.

As a first step, I'd like to modify prepareForm(), making it behave more 
like Plone's saveDataToField(). And I like to add a new kupuconfig 
option 'body_only', that allows to save only the body content, not a 
complete XHTML document.

Any objections?

@ Duncan:
Would you mind if a make some small changes in kupuploneinit.js? 
Currently it is very hard to read the diffs between kupuploneinit.js and 
kupuinit_form.js. Some whitespace / comment / order syncing would make 
it much easier.


Cheers,

	Yuppie


From duncan.booth at suttoncourtenay.org.uk  Mon Feb 12 09:21:50 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Mon, 12 Feb 2007 08:21:50 +0000 (UTC)
Subject: [kupu-dev] nbsp tags disappear, breakin' paragraphs
References: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>
	<Xns98D1AA749E088duncanrcpcouk@127.0.0.1>
	<1606606C-B498-408E-9C9C-2191909AEE21@akbild.ac.at>
Message-ID: <Xns98D2A6BE834F6duncanrcpcouk@127.0.0.1>

bernhard <g.bernhard at akbild.ac.at> wrote:

> Entering &nbsp; in html view and switching back to 'normal' kupu view  
> i found no &nbsp; any more; I looked into the dom using Firebug - no  
> &nbsp;

It doesn't appear as &nbsp; in the DOM. It will appear as character #xA0 
which, since it displays as a space is quite hard to see. I found I had 
to do 'copy html' from firebug and paste into an editor set to display 
hex codes for non-ascii characters before I could verify that the non-
break space was still there.

There is a trivial 'fix' which should get you up and running: edit 
common/kupueditor.js, find this.escapeEntities remove the 'return xml;' 
line and uncomment the 4 line return statement. That will entitise 
everything.

    this.escapeEntities = function(xml) {
	// XXX: temporarily disabled
        return xml;
        // Escape non-ascii characters as entities.
//         return xml.replace(/[^\r\n -\177]/g,
//             function(c) {
//             return '&#'+c.charCodeAt(0)+';';
//         });
    };

Unfortunately, doing that will break text indexing. An alternative 
'fix' would be:

    this.escapeEntities = function(xml) {
        // XXX: temporarily disabled
        xml = xml.replace('\xa0', '&nbsp;');
        return xml;
    };

which just escapes the non break space.

> 
> If you want to have a serious i18n aware catalog you will have to use  
> TextIndexNG - and TextIndexNG knows how to deal with html entities  
> (hopefully); I would like to know if it is hard to locate the code  
> where the entities are dropped - is it zope, plone or kupu? As long  
> as it is not Python we definitively can handle :-P  People are unable  
> to edit the image modules i put in otherwise.
> 
Kupu doesn't entitise what it saves because Plone (either currently or 
in the past, but I think it is still a problem) doesn't handle entities 
properly. When you save a document Plone uses PortalTransforms to 
convert the html to plain text before passing the plain text to 
TextIndexNG. The transform looks like (Plone 2.5.2 version):

from Products.PortalTransforms.libtransforms.retransform import 
retransform

class html_to_text(retransform):
    inputs  = ('text/html',)
    output = 'text/plain'

def register():
    # XXX convert entites with htmlentitydefs.name2codepoint ?
    return html_to_text("html_to_text",
                       ('<script [^>]>.*</script>(?im)', ' '),
                       ('<style [^>]>.*</style>(?im)', ' '),
                       ('<head [^>]>.*</head>(?im)', ' '),
                       ('(?im)</?(font|em|i|strong|b)(?=\W)[^>]*>', ''),
                       ('<[^>]*>(?i)(?m)', ' '),
                       )

Note the XXX comment which has been there for donkey's years. So what 
happens is that x&ecaute;y (or x&#xe9;y which is what kupu used to 
convert it to) is left unchanged and TextIndexNG indexes separate words 
x, eacute, y (or x, xe9, y).

I guess maybe I should attempt to do the conversion for some things like 
nbsp and leave accented letters unchanged.


From g.bernhard at akbild.ac.at  Mon Feb 12 10:11:35 2007
From: g.bernhard at akbild.ac.at (bernhard)
Date: Mon, 12 Feb 2007 10:11:35 +0100
Subject: [kupu-dev] nbsp tags disappear, breakin' paragraphs
In-Reply-To: <Xns98D2A6BE834F6duncanrcpcouk@127.0.0.1>
References: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>
	<Xns98D1AA749E088duncanrcpcouk@127.0.0.1>
	<1606606C-B498-408E-9C9C-2191909AEE21@akbild.ac.at>
	<Xns98D2A6BE834F6duncanrcpcouk@127.0.0.1>
Message-ID: <25A8E3A6-640B-4D2A-9CE2-6DB840E31A4C@akbild.ac.at>

Dear Duncan!

Now i _do_ owe you one...
Kupu is dealing with 'nbsp' entities now exactly as it is supposed  
to.  I'd suggest to make

     this.escapeEntities = function(xml) {
         xml = xml.replace('\xa0', '&nbsp;');
         return xml;
     };

default behaviour; Indexing should work perfectly well with it. If  
there is some service
as 'fleurop' or 'www.bierher.at' on your side of the screen im am  
really willing to send
you a 'surprise'...

Who said Mondays are bad?

Very Best Regards,
Gogo.
<g.bernhard at akbild.ac.at>


On 12.02.2007, at 09:21, Duncan Booth wrote:

> bernhard <g.bernhard at akbild.ac.at> wrote:
>
>> Entering &nbsp; in html view and switching back to 'normal' kupu view
>> i found no &nbsp; any more; I looked into the dom using Firebug - no
>> &nbsp;
>
> It doesn't appear as &nbsp; in the DOM. It will appear as character  
> #xA0
> which, since it displays as a space is quite hard to see. I found I  
> had
> to do 'copy html' from firebug and paste into an editor set to display
> hex codes for non-ascii characters before I could verify that the non-
> break space was still there.
>
> There is a trivial 'fix' which should get you up and running: edit
> common/kupueditor.js, find this.escapeEntities remove the 'return  
> xml;'
> line and uncomment the 4 line return statement. That will entitise
> everything.
>
>     this.escapeEntities = function(xml) {
> 	// XXX: temporarily disabled
>         return xml;
>         // Escape non-ascii characters as entities.
> //         return xml.replace(/[^\r\n -\177]/g,
> //             function(c) {
> //             return '&#'+c.charCodeAt(0)+';';
> //         });
>     };
>
> Unfortunately, doing that will break text indexing. An alternative
> 'fix' would be:
>
>     this.escapeEntities = function(xml) {
>         // XXX: temporarily disabled
>         xml = xml.replace('\xa0', '&nbsp;');
>         return xml;
>     };
>
> which just escapes the non break space.
>
>>
>> If you want to have a serious i18n aware catalog you will have to use
>> TextIndexNG - and TextIndexNG knows how to deal with html entities
>> (hopefully); I would like to know if it is hard to locate the code
>> where the entities are dropped - is it zope, plone or kupu? As long
>> as it is not Python we definitively can handle :-P  People are unable
>> to edit the image modules i put in otherwise.
>>
> Kupu doesn't entitise what it saves because Plone (either currently or
> in the past, but I think it is still a problem) doesn't handle  
> entities
> properly. When you save a document Plone uses PortalTransforms to
> convert the html to plain text before passing the plain text to
> TextIndexNG. The transform looks like (Plone 2.5.2 version):
>
> from Products.PortalTransforms.libtransforms.retransform import
> retransform
>
> class html_to_text(retransform):
>     inputs  = ('text/html',)
>     output = 'text/plain'
>
> def register():
>     # XXX convert entites with htmlentitydefs.name2codepoint ?
>     return html_to_text("html_to_text",
>                        ('<script [^>]>.*</script>(?im)', ' '),
>                        ('<style [^>]>.*</style>(?im)', ' '),
>                        ('<head [^>]>.*</head>(?im)', ' '),
>                        ('(?im)</?(font|em|i|strong|b)(?=\W)[^>]*>',  
> ''),
>                        ('<[^>]*>(?i)(?m)', ' '),
>                        )
>
> Note the XXX comment which has been there for donkey's years. So what
> happens is that x&ecaute;y (or x&#xe9;y which is what kupu used to
> convert it to) is left unchanged and TextIndexNG indexes separate  
> words
> x, eacute, y (or x, xe9, y).
>
> I guess maybe I should attempt to do the conversion for some things  
> like
> nbsp and leave accented letters unchanged.
>
> _______________________________________________
> kupu-dev mailing list
> kupu-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/kupu-dev


From g.bernhard at akbild.ac.at  Mon Feb 12 10:42:30 2007
From: g.bernhard at akbild.ac.at (bernhard)
Date: Mon, 12 Feb 2007 10:42:30 +0100
Subject: [kupu-dev] nbsp tags disappear,
	breakin' paragraphs -> supplemental
In-Reply-To: <25A8E3A6-640B-4D2A-9CE2-6DB840E31A4C@akbild.ac.at>
References: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>
	<Xns98D1AA749E088duncanrcpcouk@127.0.0.1>
	<1606606C-B498-408E-9C9C-2191909AEE21@akbild.ac.at>
	<Xns98D2A6BE834F6duncanrcpcouk@127.0.0.1>
	<25A8E3A6-640B-4D2A-9CE2-6DB840E31A4C@akbild.ac.at>
Message-ID: <92C17A78-C2D6-44EF-98D4-F5301CF35233@akbild.ac.at>

Hello again!

supplemental:
xml.replace would just replace the *first* occurance of any matches...

     this.escapeEntities = function(xml) {
         xml = xml.split('\xa0').join('&nbsp;');
         return xml;
     };

is maybe better; now it rocks.
Gogo.


On 12.02.2007, at 10:11, bernhard wrote:

> Dear Duncan!
>
> Now i _do_ owe you one...
> Kupu is dealing with 'nbsp' entities now exactly as it is supposed
> to.  I'd suggest to make
>
>      this.escapeEntities = function(xml) {
>          xml = xml.replace('\xa0', '&nbsp;');
>          return xml;
>      };
>
> default behaviour; Indexing should work perfectly well with it. If
> there is some service
> as 'fleurop' or 'www.bierher.at' on your side of the screen im am
> really willing to send
> you a 'surprise'...
>
> Who said Mondays are bad?
>
> Very Best Regards,
> Gogo.
> <g.bernhard at akbild.ac.at>
>
>
> On 12.02.2007, at 09:21, Duncan Booth wrote:
>
>> bernhard <g.bernhard at akbild.ac.at> wrote:
>>
>>> Entering &nbsp; in html view and switching back to 'normal' kupu  
>>> view
>>> i found no &nbsp; any more; I looked into the dom using Firebug - no
>>> &nbsp;
>>
>> It doesn't appear as &nbsp; in the DOM. It will appear as character
>> #xA0
>> which, since it displays as a space is quite hard to see. I found I
>> had
>> to do 'copy html' from firebug and paste into an editor set to  
>> display
>> hex codes for non-ascii characters before I could verify that the  
>> non-
>> break space was still there.
>>
>> There is a trivial 'fix' which should get you up and running: edit
>> common/kupueditor.js, find this.escapeEntities remove the 'return
>> xml;'
>> line and uncomment the 4 line return statement. That will entitise
>> everything.
>>
>>     this.escapeEntities = function(xml) {
>> 	// XXX: temporarily disabled
>>         return xml;
>>         // Escape non-ascii characters as entities.
>> //         return xml.replace(/[^\r\n -\177]/g,
>> //             function(c) {
>> //             return '&#'+c.charCodeAt(0)+';';
>> //         });
>>     };
>>
>> Unfortunately, doing that will break text indexing. An alternative
>> 'fix' would be:
>>
>>     this.escapeEntities = function(xml) {
>>         // XXX: temporarily disabled
>>         xml = xml.replace('\xa0', '&nbsp;');
>>         return xml;
>>     };
>>
>> which just escapes the non break space.
>>
>>>
>>> If you want to have a serious i18n aware catalog you will have to  
>>> use
>>> TextIndexNG - and TextIndexNG knows how to deal with html entities
>>> (hopefully); I would like to know if it is hard to locate the code
>>> where the entities are dropped - is it zope, plone or kupu? As long
>>> as it is not Python we definitively can handle :-P  People are  
>>> unable
>>> to edit the image modules i put in otherwise.
>>>
>> Kupu doesn't entitise what it saves because Plone (either  
>> currently or
>> in the past, but I think it is still a problem) doesn't handle
>> entities
>> properly. When you save a document Plone uses PortalTransforms to
>> convert the html to plain text before passing the plain text to
>> TextIndexNG. The transform looks like (Plone 2.5.2 version):
>>
>> from Products.PortalTransforms.libtransforms.retransform import
>> retransform
>>
>> class html_to_text(retransform):
>>     inputs  = ('text/html',)
>>     output = 'text/plain'
>>
>> def register():
>>     # XXX convert entites with htmlentitydefs.name2codepoint ?
>>     return html_to_text("html_to_text",
>>                        ('<script [^>]>.*</script>(?im)', ' '),
>>                        ('<style [^>]>.*</style>(?im)', ' '),
>>                        ('<head [^>]>.*</head>(?im)', ' '),
>>                        ('(?im)</?(font|em|i|strong|b)(?=\W)[^>]*>',
>> ''),
>>                        ('<[^>]*>(?i)(?m)', ' '),
>>                        )
>>
>> Note the XXX comment which has been there for donkey's years. So what
>> happens is that x&ecaute;y (or x&#xe9;y which is what kupu used to
>> convert it to) is left unchanged and TextIndexNG indexes separate
>> words
>> x, eacute, y (or x, xe9, y).
>>
>> I guess maybe I should attempt to do the conversion for some things
>> like
>> nbsp and leave accented letters unchanged.
>>
>> _______________________________________________
>> kupu-dev mailing list
>> kupu-dev at codespeak.net
>> http://codespeak.net/mailman/listinfo/kupu-dev
>
> _______________________________________________
> kupu-dev mailing list
> kupu-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/kupu-dev


From duncan.booth at suttoncourtenay.org.uk  Mon Feb 12 11:42:31 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Mon, 12 Feb 2007 10:42:31 +0000 (UTC)
Subject: [kupu-dev] nbsp tags disappear,
	breakin' paragraphs -> supplemental
References: <EA30DA00-9400-4ECE-8011-A859FA33B968@akbild.ac.at>
	<Xns98D1AA749E088duncanrcpcouk@127.0.0.1>
	<1606606C-B498-408E-9C9C-2191909AEE21@akbild.ac.at>
	<Xns98D2A6BE834F6duncanrcpcouk@127.0.0.1>
	<25A8E3A6-640B-4D2A-9CE2-6DB840E31A4C@akbild.ac.at>
	<92C17A78-C2D6-44EF-98D4-F5301CF35233@akbild.ac.at>
Message-ID: <Xns98D5660D07400duncanrcpcouk@127.0.0.1>

bernhard <g.bernhard at akbild.ac.at> wrote:

> Hello again!
> 
> supplemental:
> xml.replace would just replace the *first* occurance of any matches...
> 
>      this.escapeEntities = function(xml) {
>          xml = xml.split('\xa0').join('&nbsp;');
>          return xml;
>      };
> 
> is maybe better; now it rocks.
> Gogo.
> 
I keep forgetting that Javascript defaults to only doing one replacement. 
You want to specify the global flag which means the search string has to be 
a regex rather than a string. I think you should find this works:

        xml = xml.replace(/\xa0/g, '&nbsp;');


From g.bernhard at akbild.ac.at  Tue Feb 13 14:59:30 2007
From: g.bernhard at akbild.ac.at (bernhard)
Date: Tue, 13 Feb 2007 14:59:30 +0100
Subject: [kupu-dev] IE trouble
Message-ID: <5BD26E90-AB49-41B4-A7EE-89B7EBA6A2DE@akbild.ac.at>

I have some trouble with IE 6.0.2900 and images - Images get inserted  
at the top of the edit area, even if another image is selected (that  
happens when i try to replace one image with another); It also  
happened, when I insert one or two images lets say in the middle of  
some text paragraphs... can that be fixed or would we end up fighting  
windmills?

From duncan.booth at suttoncourtenay.org.uk  Tue Feb 13 15:29:31 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Tue, 13 Feb 2007 14:29:31 +0000 (UTC)
Subject: [kupu-dev] IE trouble
References: <5BD26E90-AB49-41B4-A7EE-89B7EBA6A2DE@akbild.ac.at>
Message-ID: <Xns98D68F7695AABduncanrcpcouk@127.0.0.1>

bernhard <g.bernhard at akbild.ac.at> wrote:

> I have some trouble with IE 6.0.2900 and images - Images get inserted  
> at the top of the edit area, even if another image is selected (that  
> happens when i try to replace one image with another); It also  
> happened, when I insert one or two images lets say in the middle of  
> some text paragraphs... can that be fixed or would we end up fighting  
> windmills?
> 

It sounds like something isn't always saving the cursor position. On which 
version of kupu are you experiencing these problems?


From mr.haalaaluu at gmail.com  Thu Feb 15 06:45:43 2007
From: mr.haalaaluu at gmail.com (Victor San Kho Lin)
Date: Thu, 15 Feb 2007 13:45:43 +0800
Subject: [kupu-dev] adding font face field in kupu plone
Message-ID: <cee7c5b00702142145p5cca2768kf011179a2363cd6d@mail.gmail.com>

Hi,

How can i add font face field in kupu on plone site.
Pls kindly point tutorial or reference.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/kupu-dev/attachments/20070215/86698628/attachment.htm 

From duncan.booth at suttoncourtenay.org.uk  Fri Feb 16 13:50:54 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Fri, 16 Feb 2007 12:50:54 +0000 (UTC)
Subject: [kupu-dev] adding font face field in kupu plone
References: <cee7c5b00702142145p5cca2768kf011179a2363cd6d@mail.gmail.com>
Message-ID: <Xns98D9816744861duncanrcpcouk@127.0.0.1>

"Victor San Kho Lin" <mr.haalaaluu at gmail.com> wrote:

> How can i add font face field in kupu on plone site.
> Pls kindly point tutorial or reference.
> Thanks.

You can't. Define paragraph styles to your css and then add them to the 
style list in kupu's configlet instead.


From dmunicio at gmail.com  Wed Feb 28 11:59:45 2007
From: dmunicio at gmail.com (Diego Municio)
Date: Wed, 28 Feb 2007 11:59:45 +0100
Subject: [kupu-dev] Kupu buttons and drawers tabindex
Message-ID: <262223130702280259x2448670fh204f4043a767189e@mail.gmail.com>

Hi all,

I have seen that kupu 1.4 doesn't have tabindex...

Well I now that in earlier versions it had a tal:attributes="tabindex
tabindex" statement for each button.
I wonder how can we access tabindex *object* defined in main_template, in
order to set tal:attributes="tabindex tabindex/next|nothing" instead.
I can access tabindex but I don't know why... Where is this variable
acquisition defined?

I also know that global_defines defines a global tabindex variable but with
pos=30000.. I couldn't find documentation about

The problem with drawers is maybe harder. As far as I know, librarydrawer
renders its contents with a xslt transform, and in drawer.xsl I cannot add
tal sentences... such as tal:atrributes="tabindex tabindex/next".

Has anybody work on this? I need to improve kupu accessibility as much as
possible and I would like to contribute if my knowledge is enough..

Thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/kupu-dev/attachments/20070228/e03ae22d/attachment.htm 

From duncan.booth at suttoncourtenay.org.uk  Wed Feb 28 12:26:35 2007
From: duncan.booth at suttoncourtenay.org.uk (Duncan Booth)
Date: Wed, 28 Feb 2007 11:26:35 +0000 (UTC)
Subject: [kupu-dev] Kupu buttons and drawers tabindex
References: <262223130702280259x2448670fh204f4043a767189e@mail.gmail.com>
Message-ID: <Xns98E573686931Bduncanrcpcouk@127.0.0.1>

"Diego Municio" <dmunicio at gmail.com> wrote:

> I have seen that kupu 1.4 doesn't have tabindex...

Can you explain why an explicit tabindex would help you? A control which 
has no explicit tabindex comes next in the order it appears in the html. 
A control which uses tabindex/next also comes next in the tabbing order. 
The only time you should see a change is when the tab index is set to 
something which isn't tabindex/next, e.g. when it gets set to 30000 for 
the search controls in the page header.

The problem is that unless you know a lot about the tabindex values used 
for the other controls around you it is almost impossible to come up 
with suitable values for tabindex.

> 
> Well I now that in earlier versions it had a tal:attributes="tabindex
> tabindex" statement for each button.
> I wonder how can we access tabindex *object* defined in main_template,
> in order to set tal:attributes="tabindex tabindex/next|nothing"
> instead. I can access tabindex but I don't know why... Where is this
> variable acquisition defined?
> 
> I also know that global_defines defines a global tabindex variable but
> with pos=30000.. I couldn't find documentation about
> 
> The problem with drawers is maybe harder. As far as I know,
> librarydrawer renders its contents with a xslt transform, and in
> drawer.xsl I cannot add tal sentences... such as
> tal:atrributes="tabindex tabindex/next".

Well you could except that it is rendered as a separate template so 
unless you know a magic number to start from you would only succeed in 
making the drawer controls appear somewhere suprising.

> 
> Has anybody work on this? I need to improve kupu accessibility as much
> as possible and I would like to contribute if my knowledge is enough..
> 
If you could start by explaining why the default tabbing isn't a good 
enough solution and what you would want to achieve by changing it.



From dmunicio at gmail.com  Wed Feb 28 13:58:43 2007
From: dmunicio at gmail.com (Diego Municio)
Date: Wed, 28 Feb 2007 13:58:43 +0100
Subject: [kupu-dev] Kupu buttons and drawers tabindex
In-Reply-To: <Xns98E573686931Bduncanrcpcouk@127.0.0.1>
References: <262223130702280259x2448670fh204f4043a767189e@mail.gmail.com>
	<Xns98E573686931Bduncanrcpcouk@127.0.0.1>
Message-ID: <262223130702280458g7040c1e2y27c58acd2c3af11a@mail.gmail.com>

First, thanks for the reply.

My problem is that I would like to insert an image in kupu by only using the
keyboard (for blind users) but I can't.

I don't know if this is a desired feature for Kupu or not but I believe that
this default behaviour is not very "Accessibility Compliant"...

In kupu 1.4, buttons tabindex are rendered as "-1" so buttons are not
getting focused with 'tab' key, so if I have understood it would be nice not
to have any "tabindex". That's no problem, I could remove them by modifying
kupu_wysiwyg_support .

Also in librarydrawer, I couldn't access the "Home", "Recent items" icons so
I made this change in drawer.xsl
(changed the 'div' to 'a' and added onkeypress event)

    <xsl:template match="library">
        <div onclick="drawertool.current_drawer.selectLibrary('{@id}');"
            class="kupu-libsource" title="{title}" style="">
            <xsl:attribute name="id">
                <xsl:value-of select="@id"/>
            </xsl:attribute>
---->      <a onkeypress="if (event.keyCode != 9 )
drawertool.current_drawer.selectLibrary('{@id}');">
                <xsl:apply-templates select="icon"/>
---->      </a>
            <span class="drawer-item-title">
                <xsl:value-of select="title"/>
            </span>
        </div>
    </xsl:template>


I could say the same with the "collection|resources" xsl:template in
drawer.xsl. I couldn't select the folders which appear in the center of the
drawer... so I added this xsl:attribute:

           <xsl:attribute name="onkeypress">
                <xsl:choose>
                    <xsl:when
                            test="local-name()='collection'">if (
event.keyCode != 9) drawertool.current_drawer.selectCollection('<xsl:value-of
select="@id"/>');</xsl:when>

                    <xsl:otherwise>if (event.keyCode != 9)
drawertool.current_drawer.selectItem('<xsl:value-of
select="@id"/>')</xsl:otherwise>
                </xsl:choose>
            </xsl:attribute>

What do you think about that?
Any comments are welcome

2007/2/28, Duncan Booth <duncan.booth at suttoncourtenay.org.uk>:
>
> "Diego Municio" <dmunicio at gmail.com> wrote:
>
> > I have seen that kupu 1.4 doesn't have tabindex...
>
> Can you explain why an explicit tabindex would help you? A control which
> has no explicit tabindex comes next in the order it appears in the html.
> A control which uses tabindex/next also comes next in the tabbing order.
> The only time you should see a change is when the tab index is set to
> something which isn't tabindex/next, e.g. when it gets set to 30000 for
> the search controls in the page header.
>
> The problem is that unless you know a lot about the tabindex values used
> for the other controls around you it is almost impossible to come up
> with suitable values for tabindex.
>
> >
> > Well I now that in earlier versions it had a tal:attributes="tabindex
> > tabindex" statement for each button.
> > I wonder how can we access tabindex *object* defined in main_template,
> > in order to set tal:attributes="tabindex tabindex/next|nothing"
> > instead. I can access tabindex but I don't know why... Where is this
> > variable acquisition defined?
> >
> > I also know that global_defines defines a global tabindex variable but
> > with pos=30000.. I couldn't find documentation about
> >
> > The problem with drawers is maybe harder. As far as I know,
> > librarydrawer renders its contents with a xslt transform, and in
> > drawer.xsl I cannot add tal sentences... such as
> > tal:atrributes="tabindex tabindex/next".
>
> Well you could except that it is rendered as a separate template so
> unless you know a magic number to start from you would only succeed in
> making the drawer controls appear somewhere suprising.
>
> >
> > Has anybody work on this? I need to improve kupu accessibility as much
> > as possible and I would like to contribute if my knowledge is enough..
> >
> If you could start by explaining why the default tabbing isn't a good
> enough solution and what you would want to achieve by changing it.
>
>
> _______________________________________________
> kupu-dev mailing list
> kupu-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/kupu-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/kupu-dev/attachments/20070228/8e476a89/attachment-0001.htm 

From emoseley at ocme.unc.edu  Wed Feb 28 16:56:13 2007
From: emoseley at ocme.unc.edu (Edmund Moseley)
Date: Wed, 28 Feb 2007 10:56:13 -0500
Subject: [kupu-dev] escape/tab to next form field
Message-ID: <1172678173.3872.2.camel@emdell>

Hi,
What would be the best method for creating a keyboard shortcut that
would allow skipping on from a kupu text area, to the next form field. 

Usually this is done with a tab, but this correctly renders a tab inside
of kupu. Any recommendations for best practices in accomplishing this?

Thanks,
Edmund


From dmunicio at gmail.com  Wed Feb 28 17:29:58 2007
From: dmunicio at gmail.com (Diego Municio)
Date: Wed, 28 Feb 2007 17:29:58 +0100
Subject: [kupu-dev] Kupu buttons and drawers tabindex
In-Reply-To: <262223130702280458g7040c1e2y27c58acd2c3af11a@mail.gmail.com>
References: <262223130702280259x2448670fh204f4043a767189e@mail.gmail.com>
	<Xns98E573686931Bduncanrcpcouk@127.0.0.1>
	<262223130702280458g7040c1e2y27c58acd2c3af11a@mail.gmail.com>
Message-ID: <262223130702280829p779a6cdbg52a1deb923fa2595@mail.gmail.com>

Sorry, I mean

-->     <a onclick="drawertool.current_drawer.selectLibrary('{@id}');"
-->        onkeypress="if (event.keyCode != 9 )
drawertool.current_drawer.selectLibrary('{@id}');"
            class="kupu-libsource" title="{title}" style="">
            <xsl:attribute name="id">
                <xsl:value-of select="@id"/>
            </xsl:attribute>
            <xsl:apply-templates select="icon"/>
            <span class="drawer-item-title">
                <xsl:value-of select="title"/>
            </span>
-->     </a>

2007/2/28, Diego Municio <dmunicio at gmail.com>:
>
> First, thanks for the reply.
>
> My problem is that I would like to insert an image in kupu by only using
> the keyboard (for blind users) but I can't.
>
> I don't know if this is a desired feature for Kupu or not but I believe
> that this default behaviour is not very "Accessibility Compliant"...
>
> In kupu 1.4, buttons tabindex are rendered as "-1" so buttons are not
> getting focused with 'tab' key, so if I have understood it would be nice not
> to have any "tabindex". That's no problem, I could remove them by modifying
> kupu_wysiwyg_support .
>
> Also in librarydrawer, I couldn't access the "Home", "Recent items" icons
> so I made this change in drawer.xsl
> (changed the 'div' to 'a' and added onkeypress event)
>
>     <xsl:template match="library">
>         <div onclick="drawertool.current_drawer.selectLibrary('{@id}');"
>             class="kupu-libsource" title="{title}" style="">
>             <xsl:attribute name="id">
>                 <xsl:value-of select="@id"/>
>             </xsl:attribute>
> ---->      <a onkeypress="if (event.keyCode != 9 )
> drawertool.current_drawer.selectLibrary('{@id}');">
>                 <xsl:apply-templates select="icon"/>
> ---->      </a>
>             <span class="drawer-item-title">
>                 <xsl:value-of select="title"/>
>             </span>
>         </div>
>     </xsl:template>
>
>
> I could say the same with the "collection|resources" xsl:template in
> drawer.xsl. I couldn't select the folders which appear in the center of
> the drawer... so I added this xsl:attribute:
>
>            <xsl:attribute name="onkeypress">
>                 <xsl:choose>
>                     <xsl:when
>                             test="local-name()='collection'">if (
> event.keyCode != 9) drawertool.current_drawer.selectCollection('<xsl:value-of
> select="@id"/>');</xsl:when>
>
>                     <xsl:otherwise>if (event.keyCode != 9)
> drawertool.current_drawer.selectItem('<xsl:value-of
> select="@id"/>')</xsl:otherwise>
>                 </xsl:choose>
>             </xsl:attribute>
>
> What do you think about that?
> Any comments are welcome
>
> 2007/2/28, Duncan Booth < duncan.booth at suttoncourtenay.org.uk>:
> >
> > "Diego Municio" < dmunicio at gmail.com> wrote:
> >
> > > I have seen that kupu 1.4 doesn't have tabindex...
> >
> > Can you explain why an explicit tabindex would help you? A control which
> > has no explicit tabindex comes next in the order it appears in the html.
> >
> > A control which uses tabindex/next also comes next in the tabbing order.
> > The only time you should see a change is when the tab index is set to
> > something which isn't tabindex/next, e.g. when it gets set to 30000 for
> > the search controls in the page header.
> >
> > The problem is that unless you know a lot about the tabindex values used
> > for the other controls around you it is almost impossible to come up
> > with suitable values for tabindex.
> >
> > >
> > > Well I now that in earlier versions it had a tal:attributes="tabindex
> > > tabindex" statement for each button.
> > > I wonder how can we access tabindex *object* defined in main_template,
> >
> > > in order to set tal:attributes="tabindex tabindex/next|nothing"
> > > instead. I can access tabindex but I don't know why... Where is this
> > > variable acquisition defined?
> > >
> > > I also know that global_defines defines a global tabindex variable but
> >
> > > with pos=30000.. I couldn't find documentation about
> > >
> > > The problem with drawers is maybe harder. As far as I know,
> > > librarydrawer renders its contents with a xslt transform, and in
> > > drawer.xsl I cannot add tal sentences... such as
> > > tal:atrributes="tabindex tabindex/next".
> >
> > Well you could except that it is rendered as a separate template so
> > unless you know a magic number to start from you would only succeed in
> > making the drawer controls appear somewhere suprising.
> >
> > >
> > > Has anybody work on this? I need to improve kupu accessibility as much
> > > as possible and I would like to contribute if my knowledge is enough..
> >
> > >
> > If you could start by explaining why the default tabbing isn't a good
> > enough solution and what you would want to achieve by changing it.
> >
> >
> > _______________________________________________
> > kupu-dev mailing list
> > kupu-dev at codespeak.net
> > http://codespeak.net/mailman/listinfo/kupu-dev
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/kupu-dev/attachments/20070228/4f2220ab/attachment.htm