Hello Hussein, I would definitely not suggest that the easy profiling add-on is useless, since I am currently ripping out the custom attribute manager you wrote for us and replacing it with the easy profiling interface.
I will suggest that applying a different kind of logic to the display of content than is applied to the actual filtering of the content when the same profiles are selected limits the usability of that aspect of the feature, and will prevent me from deploying the "styled" views of the content to my users. While it is indeed possible to apply individual styles to individual attributes, in settings that make heavy use of attributes for filtering such a display of content quickly degenerates into an incomprehensible compost of styles where the users need to constantly refer to a reference key to understand what they are looking at. The ability to simply define one style for "within the current filtering parameters" and one for "outside the current filtering parameters" was brilliant, and I was very excited until I realized that the feature's logic differed from DITA's filtering logic. As it stands, I'll just keep an eye on follow-up versions of the feature to see if this is changed. Cheers, Jeff. -----Original Message----- From: Hussein Shafie [mailto:huss...@xmlmind.com] Sent: Thursday, March 26, 2015 1:42 AM To: Jeff Hooker Cc: 'xmleditor-support@xmlmind.com' Subject: Re: [XXE] Defined profile styles appearing the 6.1 but not in 6.0 On 03/25/2015 09:14 PM, Jeff Hooker wrote > > I just read your message more closely and noticed this: > > * Common pitfall: for an element to be displayed with the style of the > selected profile or with the style of the unselected profile, this element > must have *all* the profiling attributes set on it. > > This means that the visual "profile" filtering and the actual representation > of the data that would emerge from a publishing job could be very different > does it not? > Yes. The DITA spec says: --- When deciding whether to include or exclude a particular element, a processor should evaluate each attribute, and then evaluate the set of attributes. * If all the values in a single attribute evaluate to "exclude", the attribute evaluates to "exclude". * If *any* single attribute evaluates to exclude, the element is excluded. --- Therefore when the profiles specified in the ".profiles" file use 2 profiling attributes or more, then a element may be indeed not be rendered on screen as being part of the selected profile or any unselected profile, but still be filtered out when converting the document to PDF, RTF, HTML, etc. Before saying that this makes the "Easy Profiling" add-on useless, 1) the "Easy Profiling" add-on has several other features in terms of profiling attribute editing and validation. 2) the "Easy Profiling" add-on can also style individual profiling attributes. See http://www.xmlmind.com/xmleditor/_distrib/doc/profiling/index.html Of course, may be we'll change the behavior related to the above common pitfall in a future version of XXE. May be this will even require differentiating profile rendering in DocBook and profile rendering in DITA. Not sure. Needs more thinking about it. > In the event that you are interested, here are my test files. Your test files work fine with v6.0. I've tested that. The problems you have with v6.0 but not with v6.1 probably come from your working environment. -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
