Yes, we are looking int it. -- Scott
On Aug 13, 3:37 pm, Barb <[email protected]> wrote: > Thanks Scott ... does this also include the entities that don't > resolve? > > On Aug 13, 4:24 pm, Scott Henninger <[email protected]> > wrote: > > > Barb; There are indeed differences in how the Tree and Form labels > > are displayed. We will get this on the bug list. > > > -- Scott > > > On Aug 13, 12:49 pm, Barb <[email protected]> wrote: > > > > I'm in Ensemble and have clicked on a node from my hierachy tree. The > > > metadata associated with the selected node comes up in a different > > > pane for editing. I'm editing the "label" property (I. In General) and > > > am adding a section symbol plus "ABC" (I. In General § ABC). Once > > > I hit enter, the html number code is resolved to a section symbol ... > > > ( I. In General § ABC) Seems a symbol can have both an HTML Name code > > > and an HTML Number code. Via experimentation, looks like a larger > > > percentage of number codes are successfully resolved compared to the > > > name code. Unfortunately neither are 100%. For example in the case of > > > – (–) .. Ensemble does not resolve either. Another issue is > > > that these special characters are only resolved in the pane where the > > > editing is being done. There is no resolution in the tree view, > > > results grid or the tab identifying the selected node. Should I be > > > configuring something differently in Ensemble or is this a known > > > issue? > > > > Thanks, > > > > Barb- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
