Blair, thanks for the understanding. Not sure it's worth trying to make the
XML dump any better than it is.
Jacob, neat find. Unfortunately, it's all PHP but I was able to read enough
of it to kind of reverse engineer the REST API. Did not realize that was
there. Let's see if I can quickly hack together a better migration tool
using that.
On Tue, Aug 20, 2013 at 7:48 AM, Hoover, Jacob
<jacob.hoo...@greenheck.com>wrote:
> One other possible option, if the XML is that mangled, is to utilize the
> REST API of SF. A bit of searching shows some promise (though this exports
> for a different tracker), https://github.com/NateWr/sftrackerexport****
>
> ** **
>
> ** **
>
> *From:* Blair Murri [mailto:os...@live.com]
> *Sent:* Tuesday, August 20, 2013 7:25 AM
> *To:* Windows Installer XML toolset developer mailing list
>
> *Subject:* Re: [WiX-devs] New bug database under test****
>
> ** **
>
> I figured out what was done to create the codepage mess in the dump.
> I'll determine by the end of the week the best way to parse it to get out
> something that approximates what went in.
>
> Basically this is what the forensics says happened (based on the entries
> I've dug into):
>
> In the sourceforge tracker database data is stored in utf-8.
> The export function believes that the database data is stored as
> Windows-1252 and it "converts" it into utf-8.
> It then wraps the result in XML and then tells every xml parser to
> interpret the result as Latin-1 (after having including a utf-8 BOM at the
> start of the XML file!). (we aren't schizophrenic yet, are we?)
>
> Anything that isn't ASCII is basically mangled by the above (utf-8
> interpreted as Windows-1252 converted to utf-8 and interpreted as Latin-1),
> since any conforming XML parser will ignore the BOM and do what it was told
> by the xml declaration.
>
> I'll probably create something that accepts XML as input and spits out
> correctly interpretable XML as output.
>
> Blair
>
> P.S. It appears that file attachments to items in SF's tracker are
> referenced but not included in the exported XML.
> ****
> ------------------------------
>
> From: os...@live.com
> To: wix-devs@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 02:11:47 -0700
> Subject: Re: [WiX-devs] New bug database under test****
>
> 4. I'll take a crack at it, sure. Send it over...
> ****
> ------------------------------
>
> From: r...@robmensching.com
> Date: Sun, 18 Aug 2013 07:26:08 -0700
> To: wix-devs@lists.sourceforge.net
> Subject: Re: [WiX-devs] New bug database under test****
>
> 1. Good.****
>
> ****
>
> 2. You'll get used to it. <smile/>****
>
> ****
>
> 3. Issue #13 tracks that.****
>
> ****
>
> 4. If you're really interested, I could send you the mess of an XML file
> they provide. It's a mess of data that I had to reconstruct into something
> halfway useful. ****
>
> ****
>
> If it isn't obvious, I'm pretty done dealing with SF and want to get to a
> place that can just work better. <smile/>****
>
> ** **
>
> On Sun, Aug 18, 2013 at 12:33 AM, Blair Murri <os...@live.com> wrote:****
>
> 1. I tried again, but the same error didn't repro. I'll try to catch it
> off guard again a few times. As far as I recall, it told me the account was
> activated at the time..****
>
>
> 2. Most sites I've seen use tabs, one to edit in and the other to preview.
> The more I think about it the more I like the "always live" preview, but as
> it was unexpected. Maybe a note above the edit box mentioning the preview
> below the box would have alerted to its presence and I wouldn't have
> been quite so weirded out.
>
> 3. When I tried again, I realized that my password manager didn't have
> this account in it, so I had to reset the password. That worked, but right
> after resetting the password I expected to be logged in, and when I went to
> enter my bug, it prompted me to log in (again).****
>
> 4. Maybe we could determine the codepage that SF provides?****
>
> ****
>
> Blair****
> ------------------------------
>
> From: r...@robmensching.com
> Date: Sat, 17 Aug 2013 07:43:03 -0700
> To: wix-devs@lists.sourceforge.net
> Subject: Re: [WiX-devs] New bug database under test****
>
> ** **
>
> First of all, did you do all of this before or after you activated your
> account? You can't do most things on the site until you validated the email
> address used and some error messages may not be as good as they could be in
> those cases.****
>
> ****
>
> 1. Hmm, if you successfully signed in and had activated you account that
> should work. If you have a couple minutes, could you bring up the developer
> tools in your browser (F12 in IE and Chrome), look at the networking tab,
> make sure it is capturing then hit the button. You should hopefully get a
> bit more detail about what went wrong. That would help me, I'll look into
> the issue as well.****
>
> ****
>
> 2. Well, it's a Markdown control so what you type above may be rendered
> differently below. I the preview hope this helps people that submit bugs
> because on SF without indenting XML disappears because the Markdown control
> hid it.****
>
> ****
>
> 3. That similarly should just work. But if you click on new issue but
> haven't verified your account then you're going to be prompted to sign
> in. That may have been what happened. I'll see if I can improve the error
> messages for unverified users.****
>
> ****
>
> 4. Yeah, the dump provided by SF is less than ideal.****
>
> ****
>
> ** **
>
> On Fri, Aug 16, 2013 at 10:56 PM, Blair Murri <os...@live.com> wrote:****
>
> 1. When I try to submit a bug, I get:
>
> *Error!* Something went awry while submitting your changes. Please, try
> again.
>
> There's no indication of just what did go awry, but trying again just
> repeats the error message.
>
> 2. Also, I don't know if it is cool or disconcerting to see what I am
> typing being echoed back to me in the preview area under the box I am
> typing in. It did weird me out when I first discovered it was happening.
>
> 3. I used the browser back button after logging in and looking at a couple
> bugs, then I clicked on "new issue" and had to sign in again. It would be
> nice if it didn't forget me so quickly (literally less than 30 seconds
> after I had signed in the first time).
>
> 4. I noticed on some of the bugs that appear to have been imported from SF
> that some codepage mismatch happened in the import.****
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free
> troubleshooting tool designed for production. Get down to code-level detail
> for bottlenecks, with
> _______________________________________________ WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs****
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free
> troubleshooting tool designed for production. Get down to code-level detail
> for bottlenecks, with
> _______________________________________________ WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs****
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free
> troubleshooting tool designed for production. Get down to code-level detail
> for bottlenecks, with
> _______________________________________________ WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs****
>
>
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and
> AppDynamics. Performance Central is your source for news, insights,
> analysis and resources for efficient Application Performance Management.
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
