Bugs item #1554252, was opened at 2006-09-07 17:16 Message generated for change (Comment added) made by turha You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1554252&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: candle Group: v3.0 Status: Closed Resolution: Accepted Priority: 1 Private: No Submitted By: turha (turha) Assigned to: pmarcu (pmarcu) Summary: inconsistent parsing of character and entity references Initial Comment: Windows Installer XML 2.0.4423.0 does not parse XML character references in preprocessor variable definitions, and apparently does not parse internal general entity references anywhere. Such references either appear unchanged in the resulting Windows Installer database or disappear entirely. However, WiX does parse character references and predefined entity references when they occur directly in element attributes or content, rather than in preprocessor variable definitions. The attached entity.wxs should result in a Property table where each Value field contains an apostrophe surrounded by parentheses; but WiX gives this result in only four of the twelve rows generated. Please see the comment at the end of the attachment. Should you prefer separate bug reports about character references and general entity references, please let me know, and I'll retitle this one to cover character references only and open another one about general entity references. ---------------------------------------------------------------------- >Comment By: turha (turha) Date: 2008-05-21 19:06 Message: Logged In: YES user_id=1102079 Originator: YES Did you consider setting XmlTextReader.EntityHandling = EntityHandling.ExpandEntities in the preprocessor, or handling XmlNodeType.EntityReference and calling XmlReader.ResolveEntity? ---------------------------------------------------------------------- Comment By: Rob Mensching (robmen) Date: 2008-05-16 06:45 Message: Logged In: YES user_id=991639 Originator: NO This is a core Xml thing. We're not in control at the point these get resolved. ---------------------------------------------------------------------- Comment By: pmarcu (pmarcu) Date: 2007-10-10 21:04 Message: Logged In: YES user_id=1612676 Originator: NO Same situation in 3.0. ---------------------------------------------------------------------- Comment By: Rob Mensching (robmen) Date: 2006-12-20 04:07 Message: Logged In: YES user_id=991639 Originator: NO Moving to WiX v3. There are several things in the Preprocessor that are kinda' whacky that are cleaned up in WiX v3. I'm not sure we can truly fix this bug anyway, most of this handling is by the XML DOM. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1554252&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
