Hi Barb
I am having difficulties understanding your problems here. There are issues concerning labels and prorogation of labels between things in TB Ensemble. However, these do not seem to have any connection with special characters, all of which work as well as any other characters as far as I can tell. Concerning html entities, it is not clear to me where you are expecting to be using these. In any semantic web environment, including the whole of the TopBraid Suite, Unicode is the underlying representation of text, with full support for almost any character you can dream of. If you choose to output semantic web data as XML, e.g. RDF/XML, then various characters will be escaped appropriately. It is unclear to me what other functionality you are expecting; and hence I can't give a time scale for a fix. Jeremy Barb wrote: > Can you estimate on when this fix will be available? > > On Aug 13, 5:33 pm, Scott Henninger <[email protected]> > wrote: > >> 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 -- 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 -~----------~----~----~----~------~----~------~--~---
