680 Reputation

11 Badges

4 years, 16 days

MaplePrimes Activity

These are replies submitted by Anthrazit

@Samir Khan 

I've filed a technical support request on the Maplesoft support page. In addition you've also added Maple 2021 to the list in the software change request scheme.


I've downloaded the Tex Live application for Windows, and printed one of the documents I have just to see what was happening.

The export to pdf and print to pdf gave the same results, so I assume they have the same core behind. I'm also attaching a screenshot of how the document looks on the screen.




According to the release information, the Latex converter doesn't work with components.

So even if for some workbooks the converter might give sufficient results, it won't do the job for workbooks with components.

I fully support your request, and have recently filed a similar thing to Maplesoft.

Every software that does have a closed non-open format needs to be able to export their output to a format that can be readable in the future. Calculations need to be readable by third party companies for review and check for example.


I've reinstalled 2020 again, and working on the same workbook in Maple 2020 doesn't cause any troubles.

This seems to be a new bug introduced into Maple 2021.

I found out that I can save the workbook exactly one time. The second time I try to save I get this error message.

However something needs to be done inbetween, just clicking twice on the save button doesn't trigger the problem.

Need to try to find out a bit more.

I've had a quick look at the homepage of one the company which software we used previously, before switching to Maple.

Mathcad is now on version Prime 7.0, and what's new is more or less combo-boxes for input (back again from version 15 many years ago), API guide, save as PDF (?), the possibility to convert from old legacy versions without installation of the old version, and some zoom and scroll functions.

Update from Maple 2020 to 2021 would take me at least halv a day to go through all the changes, and I wouldn't understand half of it either.

So I do not regret that we made the switch 2 years ago.


Here's a little extension to your code.

When doing the same thing in a Maple Code attachment, the characters used is 216.

This one is connected to

Which also leads to the problem that you can't compare strings from the Maple Code attachment, and components or variables from the main code.

Same thing as discussed in this thread?

There are apparently different ways to get this character in addition. shows 3 more methods, and all of them seem to work.

  • Ø
  • Ø
  • Ø

I've actually posted that one as a wishlist for 2021 as well.

Don't do that, Maple hasn't thought about that problem yet.

See that post:


...which again proves, that there isn't anything that could be called stupid question.


substring actually gives the same result, and here there is no reference to the same limitation.



a := "Øyeblikk"



SubString(a, 2 .. ())



SubString(a, 1 .. ())



SubString(a, 3 .. ())



substring(a, 2 .. ())







Either I am blind or I don't see it.


A yes to the first question, a maybe to the second.

Are you referring to something specific?

First 6 7 8 9 10 11 12 Last Page 8 of 16