search

jadenthem / google-refine

Automatically exported from code.google.com/p/google-refine
0 stars 0 forks source link

& symbol being parsed in url's in xml #263

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. load attached file
2. see item - datastream_links - datastream_link column
3. notice the url is broken at the "&" symbol

What is the expected output? What do you see instead?
* no text between xml tags should be parsed

What version of the product are you using? On what operating system?
* Google Refine Version 2.0 from google-refine-2.0-r1836.dmg
* Mac OS X 10.6.4 Snow Leopard

Please provide any additional information below.

Original issue reported on code.google.com by chr...@gmail.com on 29 Nov 2010 at 4:04

Attachments:

GoogleCodeExporter commented 8 years ago 
Actually, you *do* want text to be parsed so that XML entity replacement, etc 
can get done, but, having said that, this is already fixed in the development 
source tree.

Original comment by tfmorris on 29 Nov 2010 at 5:12

GoogleCodeExporter commented 8 years ago 
great, is there a way to download a binary of trunk or documentation on how to 
compile the source? It looks like it is a GAE project but I can't get it to 
load in GoogleAppEngineLauncher on my mac.

Original comment by chr...@gmail.com on 29 Nov 2010 at 2:59

GoogleCodeExporter commented 8 years ago 
The Developer's Guide on the wiki should help you:
http://code.google.com/p/google-refine/wiki/DevelopersGuide

Original comment by iainsproat on 29 Nov 2010 at 3:07

GoogleCodeExporter commented 8 years ago 
You might try just following this: 
http://code.google.com/p/google-refine/wiki/GetDevelopmentVersion

Original comment by thadguidry on 29 Nov 2010 at 3:08

GoogleCodeExporter commented 8 years ago 
the link in comment 4 was just what I was looking for.

Original comment by chr...@gmail.com on 30 Nov 2010 at 2:09

GoogleCodeExporter commented 8 years ago 
Issue 340 has been merged into this issue.

Original comment by tfmorris on 6 Jun 2011 at 10:32

GoogleCodeExporter commented 8 years ago 
Just for the record, this was fixed at the same time issue 61 was fixed, so 
that's where to look to see the history.

Original comment by tfmorris on 6 Jun 2011 at 10:33

GoogleCodeExporter commented 8 years ago

Original comment by tfmorris on 9 Jun 2011 at 7:58