Thread: [Xsltforms-support] No response on the CKEditor forums to question on encoding
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support
|
From: Dan M. <dan...@gm...> - 2010-03-05 14:51:11
|
I posted the question about how to NOT encode XML on post on the CKEditor forum yesterday: http://cksource.com/forums/viewtopic.php?f=11&t=17900 But I have not got any feedback. Since we can always just do a server-side parse using util:parse() this is not a problem for eXist. But I wanted to see who was watching the forums. I have tried to classify all the major configuration options of a CKEditor into around a dozen classes: Category Description Coding These options control how editor encodes various items. Configuration These options control how editor is configured and the locations that this configuration information is loaded. Initialization These options control how editor is first presented to the user. Import Text These options control initial text is imported. Keyboard These options control how characters typed on the keyboard are managed. Language These options control the language used or language-related options. Output These options control how data is output when the text is saved. Dialog These options control the behavior within specific dialog panels. Runtime These options control the non-style related user experience while the editor is running. Style These options control the presentation aspects of this extension. Options are traditionally done through a CSS file. Text Coding These options control how internal elements in the text are represented or coded as the user interacts with the editor. It might be nice to create a multi-tab XForms application to edit the most common configuration options. Note that most of the configuration options are style-related. My next step is to find out what options are the most important for our users. - Dan -- Dan McCreary Semantic Solutions Architect syntactica.com 952-460-1674 |
|
From: Rob K. <ro...@ko...> - 2010-03-05 15:12:56
|
Are you talking about character encoding or escaping XML/XHTML so it can go into a textarea? If encoding, put a content type meta in your head. If escaping, you can GET from the server and use javascript to escape the XML, and then place in a textarea. Then on save, get the value of the textarea and unescape it to PUT or POST. best, -Rob On Fri, Mar 5, 2010 at 6:51 AM, Dan McCreary <dan...@gm...> wrote: > I posted the question about how to NOT encode XML on post on the CKEditor > forum yesterday: > > http://cksource.com/forums/viewtopic.php?f=11&t=17900 > > But I have not got any feedback. > > Since we can always just do a server-side parse using util:parse() this is > not a problem for eXist. But I wanted to see who was watching the forums. > > I have tried to classify all the major configuration options of a CKEditor > into around a dozen classes: > > Category Description Coding These options control how editor encodes > various items. Configuration These options control how editor is > configured and the locations that this configuration information is loaded. > Initialization These options control how editor is first presented to the > user. Import Text These options control initial text is imported. > Keyboard These options control how characters typed on the keyboard are > managed. Language These options control the language used or > language-related options. Output These options control how data is output > when the text is saved. Dialog These options control the behavior within > specific dialog panels. Runtime These options control the non-style > related user experience while the editor is running. Style These options > control the presentation aspects of this extension. Options are > traditionally done through a CSS file. Text Coding These options control > how internal elements in the text are represented or coded as the user > interacts with the editor. > It might be nice to create a multi-tab XForms application to edit the most > common configuration options. > > Note that most of the configuration options are style-related. My next > step is to find out what options are the most important for our users. > > - Dan > > -- > Dan McCreary > Semantic Solutions Architect > syntactica.com > 952-460-1674 > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Dan M. <dan...@gm...> - 2010-03-05 15:32:56
|
Hi Rob, Thanks for your note. I agree that the world "encode" has many meanings. Sorry if I was not clear. I am trying to get CKEditor to not encode the HTML/XML it sends using the < and > notation when it does a post to the eXist server after the user does a save. For example: <p>hello world</p> Is being submitted to the server as: <p>hello world</p> >From what I can tell, CKEditor does this by default and I can not seem to be able to turn it off on the client reguardless of the config file settings I use. Since it is easy to unencode the post data on the server side with the XQuery util:parse() function it is really just a small issue. It just that every single < and > takes four characters when only one is needed. Has anyone else got this to work? - Dan On Fri, Mar 5, 2010 at 9:12 AM, Rob Koberg <ro...@ko...> wrote: > Are you talking about character encoding or escaping XML/XHTML so it can go > into a textarea? > > If encoding, put a content type meta in your head. > > If escaping, you can GET from the server and use javascript to escape the > XML, and then place in a textarea. Then on save, get the value of the > textarea and unescape it to PUT or POST. > > best, > -Rob > > > > On Fri, Mar 5, 2010 at 6:51 AM, Dan McCreary <dan...@gm...>wrote: > >> I posted the question about how to NOT encode XML on post on the CKEditor >> forum yesterday: >> >> http://cksource.com/forums/viewtopic.php?f=11&t=17900 >> >> But I have not got any feedback. >> >> Since we can always just do a server-side parse using util:parse() this is >> not a problem for eXist. But I wanted to see who was watching the forums. >> >> I have tried to classify all the major configuration options of a CKEditor >> into around a dozen classes: >> >> Category Description Coding These options control how editor encodes >> various items. Configuration These options control how editor is >> configured and the locations that this configuration information is loaded. >> Initialization These options control how editor is first presented to the >> user. Import Text These options control initial text is imported. >> Keyboard These options control how characters typed on the keyboard are >> managed. Language These options control the language used or >> language-related options. Output These options control how data is >> output when the text is saved. Dialog These options control the behavior >> within specific dialog panels. Runtime These options control the >> non-style related user experience while the editor is running. Style These >> options control the presentation aspects of this extension. Options are >> traditionally done through a CSS file. Text Coding These options control >> how internal elements in the text are represented or coded as the user >> interacts with the editor. >> It might be nice to create a multi-tab XForms application to edit the most >> common configuration options. >> >> Note that most of the configuration options are style-related. My next >> step is to find out what options are the most important for our users. >> >> - Dan >> >> -- >> Dan McCreary >> Semantic Solutions Architect >> syntactica.com >> 952-460-1674 >> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> > -- Dan McCreary Semantic Solutions Architect syntactica.com 952-460-1674 VOIP: 111@69.199.167.229 |
|
From: Rob K. <ro...@ko...> - 2010-03-05 15:43:52
|
You probably have to bind to the submit event (you can use jquery for this type of thing or stick an onsubmit='return mySubmitHandler()' on the form). Then, before you send to the server, use the built in javascript unescape(& lt;p>hello world</p>) best, -Rob On Fri, Mar 5, 2010 at 7:32 AM, Dan McCreary <dan...@gm...> wrote: > Hi Rob, > > Thanks for your note. I agree that the world "encode" has many meanings. > Sorry if I was not clear. > > I am trying to get CKEditor to not encode the HTML/XML it sends using the > < and > notation when it does a post to the eXist server after the > user does a save. > > For example: > > <p>hello world</p> > > Is being submitted to the server as: > > <p>hello world</p> > > >From what I can tell, CKEditor does this by default and I can not seem to > be able to turn it off on the client reguardless of the config file settings > I use. Since it is easy to unencode the post data on the server side with > the XQuery util:parse() function it is really just a small issue. It just > that every single < and > takes four characters when only one is needed. > > Has anyone else got this to work? > > - Dan > > On Fri, Mar 5, 2010 at 9:12 AM, Rob Koberg <ro...@ko...> wrote: > >> Are you talking about character encoding or escaping XML/XHTML so it can >> go into a textarea? >> >> If encoding, put a content type meta in your head. >> >> If escaping, you can GET from the server and use javascript to escape the >> XML, and then place in a textarea. Then on save, get the value of the >> textarea and unescape it to PUT or POST. >> >> best, >> -Rob >> >> >> >> On Fri, Mar 5, 2010 at 6:51 AM, Dan McCreary <dan...@gm...>wrote: >> >>> I posted the question about how to NOT encode XML on post on the CKEditor >>> forum yesterday: >>> >>> http://cksource.com/forums/viewtopic.php?f=11&t=17900 >>> >>> But I have not got any feedback. >>> >>> Since we can always just do a server-side parse using util:parse() this >>> is not a problem for eXist. But I wanted to see who was watching the >>> forums. >>> >>> I have tried to classify all the major configuration options of a >>> CKEditor into around a dozen classes: >>> >>> Category Description Coding These options control how editor encodes >>> various items. Configuration These options control how editor is >>> configured and the locations that this configuration information is loaded. >>> Initialization These options control how editor is first presented to >>> the user. Import Text These options control initial text is imported. >>> Keyboard These options control how characters typed on the keyboard are >>> managed. Language These options control the language used or >>> language-related options. Output These options control how data is >>> output when the text is saved. Dialog These options control the >>> behavior within specific dialog panels. Runtime These options control >>> the non-style related user experience while the editor is running. >>> Style These options control the presentation aspects of this extension. >>> Options are traditionally done through a CSS file. Text Coding These >>> options control how internal elements in the text are represented or coded >>> as the user interacts with the editor. >>> It might be nice to create a multi-tab XForms application to edit the >>> most common configuration options. >>> >>> Note that most of the configuration options are style-related. My next >>> step is to find out what options are the most important for our users. >>> >>> - Dan >>> >>> -- >>> Dan McCreary >>> Semantic Solutions Architect >>> syntactica.com >>> 952-460-1674 >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>> >>> >> > > > -- > Dan McCreary > Semantic Solutions Architect > syntactica.com > 952-460-1674 > VOIP: 111@69.199.167.229 > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X