@maple fan I'm having some trouble following this thread. Are you saying that you doubt that cos(70) = 0.633319 to six decimal places?! Any scientific pocket calculator can tell you that that's correct. Do you doubt Kitonum's result that that value can be obtained using 122 terms of the series and 40 digits precision?

@ilia_mahan No one can help you because "simplify [expression A] according to [expression B]" doesn't mean anything in mathematical English (except possibly in the case where we assume that B is 0, but that is clearly not what you mean by it). Perhaps if you provided a few simple examples of one expression being "simplified according to" another expression, we could figure it out from there.

@Axel Vogt Surely you intended to say "any piecewise constant function" instead of "any piecewise function".

@Andriy Nothing unusual is happening for you. That's just the way 2D-Math "works"---another reason to not use it. This is why you see so many posts on MaplePrimes where plaintext code looks like a solid block with no line breaks.

@ANANDMUNAGALA If you had that procedure, why did you ask this Question?

If you could point me to a web-based discussion of the algorithm, I may be able to code it in Maple.

@ANANDMUNAGALA Please submit a Maple file, not a Word file!

@ANANDMUNAGALA There is no file. Please try uploading again.

@NicholasMarrone Your worksheet failed to attach. Please try again.

The OP's Question is specifically about cutting and pasting code from Maple IDE to plaintext. Maple IDE is a separately sold GUI to Maple for large-scale code development (see http://www.maplesoft.com/products/toolboxes/IDE/). So, the OP's Question has nothing to do with cutting and pasting from Maple's Standard GUI (in 1D- or 2D-input form) or Classic GUI. 

I ask the OP: Why do you want to copy to Notepad? Doesn't the IDE provide everything that you need for editing plaintext Maple files?

I don't use the IDE so I don't know the following: Does the IDE have an Export to plaintext command? Does it store your Maple code files in plaintext form? 

The MaplePrimes's Question headers should be updated to include Maple IDE as one of the product choices.

@bogo No, evalhf is not what you need; fnormal is what you need. With evalhf you have no control over the magnitude below which numbers become zero.

evalhf(1e-87);

fnormal(1e-87, 50);

     0.

The 50 is to set the precision. With this setting, any value with magnitude lower than 1e-48 is set to zero.

The only reason that I brought up evalhf was to explain that some small numbers would be automatically converted to zero.

@Markiyan Hirnyk Your advice about interface(displayprecision= ...) needs a proviso/warning: This only affects the way that the numbers are displayed; it does not change the way that they are stored or how they are used in computations. The other command, fnormal, does change the way that a number is stored and used.

@acer Don't read too much intention into the while condition in my ad hoc code. What happened was that I first decided to look for all the roots in 0..10000, regardless of how many. Then I changed my mind and decided to look for the first 20, to compare with Kitonum's list. But I forgot to remove the while condition.

Needing to use a finite maxdistance is annoying, but not as annoying as using fsolve's avoid.

@tomleslie The command verify(A, B, simplify) is (I believe) equivalent to evalb(simplify(A-B)=0). (Can someone who knows more verify that?) I do not deny that this is a very powerful technique for proving expressions equivalent---much more powerful than your earlier attempts with (effectively) evalb(simplify(A) = simplify(B)). And when that verify command returns true, I am prepared to believe it 100%: A and B are mathematically equal for all complex number substitutions for which they are defined. I am more skeptical when it returns false. I am skeptical because I don't believe that it can ever return FAIL. (Certainly it can never return FAIL if it is indeed equivalent to the evalb that I gave.) Yet is(A=B) can return FAIL. Even so, I can fairly easily create an expression A which is mathematically identically zero but such that is(A=0) returns false. (This of course indicates a bug in is.) So, I am even skeptical when is returns false, but less skeptical than for verify(..., simplify). Hence I like to verify false results by finding an explicit substitution of variable values that show the expressions are not equal.

@bfathi You say "as you can see in picture", but I can't see it---the pictures are too small. Please upload a worksheet using the green uparrow that is the last item on the second row of the toolbar in the MaplePrimes editor.