Insert from Word uses <p> for line breaks instead of <br>.

 

This makes the inserted document incorrect. How to fix this?

 

 

fredd,

 

When using pasteWord option, Cute Editor didn't use link breaks to parse your content.

 

If your content uses div, Cute Editor will use Div.

 

If your content uses P, Cute Editor will keep P.

 

If your content users br, Cute Editor will not change it either.

 

 

I should have said DIV, not BR

 

That's not what's happening, Adam,

 

Our Editor is set to use DIV:

 

Editor1.BreakElement = BreakElement.Div

 

But the pasteWord doesn't replace the <p> tags

 

 

 

fredd,

 

This is by design.

 

PasteWord just clean up the HTML code.

 

 

 

 

What do you mean, it's "by design"? Whose design idea was this? When I paste Word in FreeTextBox or FTB, it pastes correctly, so please fix CuteEditor.

 

If it "clean(s) up the HTML code", then replace the <p> tags with the Editor's setting, please. That's part of cleaning up the HTML code.

 

Please fix this bug.

 

Hi Fredd,

 

I think what Adam is trying to say is that the paste word option only removes specific microsoft code, but doeesn't actually alter the valid HTML.

 

e.g. When pasting from word you may get the following:

 

<p class="MsoNormal"><em style="mso-bidi-font-style: normal"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial">This is some text copied from word<o:p></o:p></span></em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style: normal"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial"><o:p>&nbsp;</o:p></span></em></p>
<h3><span lang="EN-GB">And another paragraph</span></h3>

 

is cleaned to :

 

<p><em><span>This is some text copied from word</span></em></p>
<p><em>&nbsp;</em></p>
<h3><span>And another paragraph</span></h3>

 

By removing the microsoft specific  code (i.e. style="mso-bidi-font-style: normal", etc).

 

It doesn't change a p to a div (or visa versa).

 

I think what you might be after is to use the Pase Text option which removes all HTML formatting.

 

Thanks,

Ady

Thanks, I know what he's saying, Ady...

 

The point is, he has code control over the paste and clean function and therefore should clean up the code to respect the Editor's settings which, in this case, is DIV for the break element.

 

Making the user do a find and replace (replacing <p> with <br>) is the wrong thing if this is to be a professional product, IMO. It's supposed to be user-friendly and every effort to make it that should be taken, especially when it comes to Word. Word users expect - quite rightly - a complete solution.

 

Our users are already screaming about the number of bugs and this just adds to our problems.

Hi Fredd,

 

It depends on your point of view, to what the function should do. What you may expect it to do may be different from how someone else may expect it to do. Therefore fixing what you may see as a bug, might cause problems with the way someone else is using the product.

 

To be honest, the way the function currently works is how I'd expect it to work, by removing the unnessessary microsoft styles added by word, but not actually changing the structure of the HTML. But that is my point of view. Perhaps 'cleaning' is an incorrect term to be using. The user manual says that it "pastes text copied from microsoft word and removes the web-unfriendly tags". It doesn't say it would modify p's to div's (which are both valid tags), and as such I wouldn't expect it to.

 

PasteText just pastes the plain text from the clip board (no bold, or other formatting either). New lines are replaced with <br /> tags regardless of the BreakElement setting. In this scenario I think it would make more sense to use the BreakElement setting because the editor is 'inserting' HTML into the pasted text, and as such I'd expect it to use the editors setting.

 

Many Thanks,

Ady

 

 

 

 

Ady,

 

CleanWord in FreeTextbox, FTB and others we tested don't exhibit this problem. So CuteEditor shouldn't either. Clean means clean. If the current default settings use DIV, br or whatever, the clean function should abide by it.

 

Respect the end-user and don't look at this from a technical viewpoint. Users are NOT expected to have to spend a ton of time cleaning what is supposed to be clean.

 

Look at editors that actually import Word docs - like Googel Docs - and not just paste them. Do you really think developers would buy the product and people would use them if they weren't as close to the original as possible?