Thanks.
On Fri, Jul 22, 2011 at 5:40 PM, Robert Perona wrote:
> I downloaded the source and changed the compiler and linker to use null,
> \x0, instead of tab, \t, and it resolved the problem confirming my earlier
> suspician. I will open it as a bug.
> On Fri, Jul 22, 2011 at 10:48 AM, Robert Pe
I downloaded the source and changed the compiler and linker to use null,
\x0, instead of tab, \t, and it resolved the problem confirming my earlier
suspician. I will open it as a bug.
On Fri, Jul 22, 2011 at 10:48 AM, Robert Perona wrote:
> I experimented some more with orca after looking at the "
I experimented some more with orca after looking at the "Archive File
Format"
in the MSI SDK, and saw the translation of tabs to char 16(DLE).
>From digging into the source, it appears the compiler uses a tab
delimited intermediate format to pass custom table rows to the linker,
however it does no
Hmm, we escape IDT chars to allow tabs to flow through. The issue is
probably just to allow CustomTable/Column to set the "escape chars" bit.
On Wed, Jul 20, 2011 at 5:53 PM, Bob Arnson wrote:
> On 20-Jul-11 17:59, Robert Perona wrote:
> > When there are tabs in the custom table data a compilati
On 20-Jul-11 17:59, Robert Perona wrote:
> When there are tabs in the custom table data a compilation error occurs, as
> if the compiler thinks the tab is attempting to create another column.
> I have tried an actual tab, xml escaped tab ( ), and msi escaping a tab
> ([{tab}], where {tab} is an act
Try representing it as
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
From: Robert Perona
To: wix-users@lists.sourceforge.net
Sent: Wednesday, July 20, 2011 4:59 PM
Subject: [WiX-us
6 matches
Mail list logo
