http://www.mapleprimes.com/posts/135657-Convertidentifier en-us 2026 Maplesoft, A Division of Waterloo Maple Inc. Maplesoft Document System Wed, 10 Jun 2026 11:06:12 GMT Wed, 10 Jun 2026 11:06:12 GMT The latest comments added to the Post, convert/identifier http://www.mapleprimes.com/images/mapleprimeswhite.jpg http://www.mapleprimes.com/posts/135657-Convertidentifier http://www.mapleprimes.com/posts/135657-Convertidentifier?ref=Feed:MaplePrimes:convert/identifier:Comments#comment135660 <p>Do you really mean computing with identifiers, i.e. TypeMK representations of objects?</p> <p>About the color of brackets, compare the outputs of:</p> <pre>`#mfenced(mfrac(mi("a"),mi("b")))`; Typesetting:-mfenced(mfrac(mi("a"),mi("b"))); </pre> The latest comments added to the Post, convert/identifier 135660 Thu, 05 Jul 2012 13:29:24 Z Alejandro Jakubi Alejandro Jakubi http://www.mapleprimes.com/posts/135657-Convertidentifier?ref=Feed:MaplePrimes:convert/identifier:Comments#comment135663 <p><a href="http://www.mapleprimes.com/posts/135657-Convertidentifier#comment135660">@Alejandro Jakubi</a>&nbsp;By "computing with identifiers" I meant just using them only as names, not parsing them. Clearly typeset names which <em>look</em> the same would also have to <em>be</em> the same (internally), or else mixing them arithmetically and otherwise would not be so useful.</p> <p>Thanks, about the brackets.</p> <p>By trying a few tricks I got some hints that Typesetting:-Typeset may not get called at all when one does right-click conversion to Atomic Identifier. That makes getting the exact same structures problematic. It'd be easier to use the same basic mechanism, than to fix up the results from something else.</p> The latest comments added to the Post, convert/identifier 135663 Thu, 05 Jul 2012 15:40:24 Z acer acer http://www.mapleprimes.com/posts/135657-Convertidentifier?ref=Feed:MaplePrimes:convert/identifier:Comments#comment135683 <p>Yes. The problem, as I see it, is that typically a large number of different TypeMK names could be created that look the same. So, without parsing them, I do not see how you could be sure that they share the same "canonical" representation for interoperation. Presumably, the standard way of handling them would be as in 2D input, passing them through the 2D parser, and operating on the resulting DAGs.&nbsp;</p> The latest comments added to the Post, convert/identifier 135683 Fri, 06 Jul 2012 07:51:04 Z Alejandro Jakubi Alejandro Jakubi