@dharr 
If I add

value(%)

to your code snippet it does not remove the invisible multiplication. What I want to achive is the following: Create input (parameter sets) that prints as described in my original post and then use the input in subsequent calculations where the invisible inert multiplication is removed by the value command.

Technically we could define a name that prints as "1 mm" and later replace it with 1*Unit('mm'). The drawback is that this has to be done for each unit separately.

Here is another way to define an inert number. Replacement requires the use of subs/eval and entering the correct replacement expression, which would not be required if a solution with the value command could be found.

Edit (code replaced)

Download Inert_num.mw

Maybe there is a way of defining a new operator an making it print invisilbe and responsive to value, which could be extended with special "simplification" rule.

If it turns out that command extension is required for value, another extendable command would equally be suitable.

Edit (replaced code)

Download Inert_one.mw

@dharr 

I have installed an older version of Acrobat. Maybe this installed an older Adobe printer (and removed a preinstalled Adobe printer)

@Ronan 

Thank you for checking.

I tried it on a different machine also with Maple 2023. It was still not working.

Changing the printer from Abode to Freepdf, it looks good now.

Which printer did you use?

@dharr 

That makes sense. Following your answer I reread ?names.

I noticed that Maple automatically inserts a space when a number followed by a letter is typed. 

The opposite (letter followed by a number) is possible to enter because it is interpreted as a name.

A number followed by a space and a letter throws the error. So my original assumption that three factors are required is incorrect. 

A close look at the output 

shows where the operation is missing. It should be better contrasted (at least it isn't on my screen). If the error message only relates to multiplication it should state "missing multiplication". This would help everyone.

If nothing speaks against it I will suggest both (better highlighting and more specific error message) items as an improvement for future software versions.

@acer 

"With steps to reproduce" I thought more about reproducing the incomplete output. I saw this before the repeated equation labels appeared. So maybe there is annother bug. My first impression was that only one line of information is quite short for infolevel:=5 but did not consider that to be a malfunction.

@acer 

• open https://www.mapleprimes.com/view.aspx?sf=243654_question/repeated_equation_labels.mw
• execute the first two inputs
• insert a new document block after DEtools:-odeadvisor(ode[1])
• cut/paste DEtools:-odeadvisor(ode[1]) into new document block
• execute the second input

with Maple 2025 and 2026 performed

repeated_equation_labels_-_after_moving_odeadvisor_command.mw

@acer 

I still do not get the full output of dsolve with infolevel[dsolve]:= 5 when I move DEtools:-odeadvisor(ode[1]) to a new document block. A restart is required. 

Thanks 

@nm 

This will also be quite usefull elsewhere. However, I have to get better at type selection for subsindets. Thanks!

@acer 

This must be a language problem on my side. I have tried to resolve the contradiction by rewriting the original post. I have also removed the questions about absorbing a factor under a root but left a link to the original document. Absorbtion is inverse to the extraction of a factor from a radical which was sufficiently discussed in the former post.

@acer 
The only reason why I desire from time to time to rearrange Maple output is to make it easier understandable or to better match math formating conventions/habits. It's for communication not for doing math. Such output can be considered final. 

In this particular case, factoring/collecting (1+x) is something what most people would do by hand or other CAS do. An outsider would probably judge from Maple's output that the math engine is not as sophisticated as other engines. 

Other examples of Maple output that I like to change are the leading minus sign when Maple applies automatic sorting or the sqrt(2)/2 factor instead of dividing by sqrt(2).

With Maple clean document are possible. Maplesoft can be proud of it. To make a document even better a final touchup is desirable (from time to time). Hence Q1. (Q2 and Q3 are more to see whehere are better techniques).

Comming back to Q1. If there are no better ways collecting (x+1), that are ideally self-explaining, I would do the following

a = 1 + x;
isolate(%, x);
subs(%, %%, expr);

Are there really no other ways?

@nm 

I have submitted a software change request. Maple does not seem to recognise in this case that numerator and denominator contain polynoms with same primitive parts (but of different powers). Primitive parts, if I understand correctly, are fundamental in algebra and can be used to normailize expression. This probably also explains why evala sometimes is helpfull at simplifing expressions. 

Only if combine is used with my original assumptions, sqrt(2) is extracted and a subsequent simplify is effective with assumptions on beta. Intuetively I would not have expected that combine can extract sqrt(2).

I stopped trials with your assumption -1 < x which indicates that the result is valid for a larger domain. How to get there with Maple?

Output[61] without using a combine command is of course reason enough that Maplesoft has close look.

221298  
228066 

@acer @dharr

Thank you

Maybe an alternative:

In the view tab on the ribbon is an option where mouse scrolling worked on my Windows 11 installation. 

Using it involves quite some clicks and mouse movements...

The problem is that is can get "polutet" with Help Pages.

@acer 

Too bad that your utilities have dissapeared. They might have adressed a niche topic but there will allways be users striving for simplicity (in code and results) beyond looking for pragmatic solutions.

(Dumb and boring) AI is not a help here and I do not see an (affordable) AI agend testing "all" combinations of Maple commands with brute force anytime soon. 

I keep it with Leonadro Da Vinci who supposedly said:

Simplicity is the ultimate sophistication.