@nm You seem to have linked to this same page, rather than to some older Question thread.

It looks as if the $ terminator has been added at the end of the parameter specification of,
    XMLTools:-NSXML:-ParseFile
which means that it's only accepting explicitly specified parameters (which doesn't include, say prolog::boolean).

Do you have an example of an input file for which option prolog=true passed to ParseFile made a concrete difference in some earlier Maple version?

ps. I have a hazy recollection that the internal parser being used by ParseFile may have been switched at some point in the past. But I don't know whether it might have just silently ignored prolog=true after that.

What would you want to happen to, say,

    sqrt(2)/14?

Would you want it to become

    1/(7*%sqrt(2))

?

limit(S2, c__1=infinity);

     y(x) = x exp(2 Pi)

odetest(%, ode);

           0

@C_R On Linux the users Favorites palette items are stored in a file separate from the GUI preferences file.

On Linux (at least), it is a file named   Favorites.properties

Perhaps you had such a file from an earlier version (say, 2025) under your Maple folder,
    C:\Users\<User ID>\AppData\Roaming\Maple
and that got imported into your new Maple 2026 installation even though you did not import the other maple.ini regular GUI preferences file.

@C_R That's really great to hear, that you're up and running ok.

If it's not too much trouble, could you please send both your Maple 2025 and the problematic "imported" Maple 2026 maple.ini preferences file (suitably renamed, say) to tech support. I can imagine that a GUI developer might be interested in trying to deduce what went awry.

@C_R Then I suggest that you send an email with a full description of all your Maple 2026.0 GUI problems (including those I mentioned above), as well as details of your OS, to
    support@maplesoft.com

Your 2026.0 installation appears to be broken in several serious ways, including at least these:

- palettes malfunctioning
- Expression Labels malfunctioning
- Help-page output malfunctioning

I somehow doubt that these are all broken in every 2026.0 installation on Windows 11 (the most common platform). I'd be surprised if Maplesoft's QA team had not noticed that all these were faulty.

It's possible that there's something special about your machine (eg. language pack, or other...).

Have you tried uninstalling and then re-installing?

At this point I suggest contacting Maplesoft's technical support directly, rather than posting various distinct Mapleprimes threads about features giving problems.

@Andiguys So, did this work for you?

I've submitted a bug report against this.  (...noting that in some versions I couldn't interrupt the original example call.)

For such problems, it's not a bad idea to directly submit a report.

Does it switch back to 2D Output in the Help Examples if you toggle the input back to 2D?

@alexsid I see the same thing in Maple 2026 (and 2025) when running under the GNOME desktop management system (default) on Linux ubuntu 24.04 LTS.

I have (almost) trained my wrist to not slide the mouse pointer over to the right of Recent Documents, when the full list pops up, but instead use the arrow keys to move the highlighted selection up or down. Often it takes a few tries.

I'm a little slow and half figured it might be intentional. But now I'll submit a bug report.

You can pass a list of three items to plot3d, along with the option plotlist, to denote that it's not intended as a parametric plot.

This is documented in the 8th bullet point of the Description section of the plot3d Help-page.

Dr.D-N_ac.mw

Note that if you use a set rather than a list then its items may get re-ordered and subsequently no longer be correspond as intended to the colors (or other options) also supplied in lists. That might not happen in this particular example, due to a fortuitous set-ordering (lexicographic, etc). But in general it's not the case.

After a little investigation it seems that the situation might be slightly more complicated.

A routine in simplex is calling solve, and it is under there (SolveTools:-Tranformer) that Normalizer gets used for this example.

And there's some frontend in play. And the waters are muddy, as that SolveTools routine uses a custom variant of Testzero (not the default of leveraging current Normalizer). And that calls normal rather than Normalizer. And I find simplex:-do-pivot's use of series curious.

And I'm not yet completely sure that my success using a stronger Normalizer didn't just "luck out".

I will submit a bug report.

@nm It is slower to use allvalues on the result from PolynomialTools:-Split for this example, and Alfred specifically asked about factors in terms of radicals.

So constructing from the (optionally simplified) radical results obtained from your original solve(...,x,explicit) suggestion seems ok.