From: Robert P. <rob...@gm...> - 2012-04-16 20:09:51
|
The parser seems to handle the entities just fine, but it looks like the upgrade script failed. On Mon, Apr 16, 2012 at 3:21 PM, Marc Laporte <ma...@ma...> wrote: > Here: https://trunkinfo.tiki.org/Join+the+Community > > Code plugin shows: > <a href="http://tiki.org" title="Powered by > Tiki"> > <img src="IMAGE LOCATION ON YOUR SERVER" > alt="Powered by Tiki" style="border:0" > width="80" height="15" /> > </a> > > Thanks! > > On Mon, Apr 16, 2012 at 3:05 PM, Marc Laporte <ma...@ma...> > wrote: > > The state as of now in 9.x is incorrect not just for WYSIWYG > > > > See: https://trunkinfo.tiki.org/HTMLentities > > > > We see &eacute; instead of é > > > > Thanks! > > > > > > On Mon, Apr 16, 2012 at 12:07 PM, Robert Plummer > > <rob...@gm...> wrote: > >> On a second look, it looks like the only problem is at the time of > editing > >> with html off: > >> > >> <list> is seen as html with wysiwyg editor, so not sure how to fix that > >> honestly. When the page loads up after edit, things are seen correctly, > >> <list> is <list>. > >> > >> Jonnyb, you following? > >> > >> > >> On Mon, Apr 16, 2012 at 11:44 AM, Robert Plummer > >> <rob...@gm...> wrote: > >>> > >>> Hey Guys, > >>> I've tried to clean up the parser as much as possibly while using html > >>> entities. The biggest problem i see right now is the use of html in a > page > >>> with wysiwyg on. The problem is that wysiwyg parses a page a few > times, I > >>> feel that it should parse just like normal and that the output should > be an > >>> alternative to the standard edit more, but the issue is that the > output is > >>> different from what is stored.... > >>> > >>> < becomes &lt; for example, so I've not found a good way to fix > >>> that, but I am running out of time that I can spend on something this > >>> trivial. I feel that qysiwyg is experimental and until all these > little > >>> issues are worked out, i feel it may need to be moved back to > experimental > >>> till those issues can be addressed. It might be something very small, > very > >>> easily fixable, but I need to devote the majority of the rest of the > time I > >>> have available to ensuring the big problems with tiki are fixed. > >>> > >>> Please let me know if anyone wants to look into this. Jyhem, you want > to > >>> take a stab at it? > >>> > >>> Lastly, I don't mind jumping into the parser because I've worked with > >>> parsers before and can wrap my head around it fairly well, but Tiki's > wiki > >>> parser needs a makover so that you don't need to wrap your mind around > it, > >>> it is just understandable. I would like to bring this up in our next > >>> webinar if possible, and step through with developers how easy it is to > >>> create a very stable parser for wiki syntax. > >>> -- > >>> Robert Plummer > >> > >> > >> > >> > >> -- > >> Robert Plummer > >> > >> > ------------------------------------------------------------------------------ > >> For Developers, A Lot Can Happen In A Second. > >> Boundary is the first to Know...and Tell You. > >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > >> http://p.sf.net/sfu/Boundary-d2dvs2 > >> > >> _______________________________________________ > >> TikiWiki-devel mailing list > >> Tik...@li... > >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > >> > > > > > > > > -- > > Marc Laporte > > > > http://MarcLaporte.com > > http://Tiki.org/MarcLaporte > > http://AvanTech.net > > > > -- > Marc Laporte > > http://MarcLaporte.com > http://Tiki.org/MarcLaporte > http://AvanTech.net > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > -- Robert Plummer |