Doc

If you got a blank .xml file then chances are the file you tried to convert was not exported from Promash, or has been modified and certain tags removed since it was.It should have told you of this too.

OK, thanks, got it to work. Ã‚Â The problem is that the conversion script requires certain ProMash "options" set in order to perform the conversion. Ã‚Â I set all the options, including ones that I didn't think made a difference. Ã‚Â So if the conversion doesn't work set all the options.

I had a legit text output from ProMash with NO deletions. Ã‚Â I tried an old and a new text export, apparently with not the right options set. Ã‚Â The script did not inform me I was missing anything.Comparing the text you sent (which worked) to mine revealed "missing" data in mine.

To Use This Tool1. Open your recipe in Promash and export it as a TEXT file format. 2. Run the visual basic script (link provided below). 3. Choose the TEXT file Promash format as the Source Recipe. 4. Choose the BeerXML file to export the recipe as. 5. Read the BeerXML file into your favorite BeerXML compatible program!

to

To Use This Tool1. Open your recipe in Promash and print/export it in TEXT file formatwith all text options selected.2. Run the visual basic script (link provided below). 3. Choose the TEXT file Promash format as the Source Recipe. 4. Choose the BeerXML file to export the recipe as. 5. Read the BeerXML file into your favorite BeerXML compatible program!

Doc

However there is some logic in the conversion as I encountered similar problems in my testing, when sent recipes from some of the beta testers, where not full text exports were done from Promash.The conversion script does NOT require all parts of the Promash recipe to be there, but does require at least a base set in the right Promash order.

From the top. The conversion script expects to see the line "A ProMash Recipe Report"

Then it expects to see "Style Guidelines"Then it expects to see "Recipe Specifics"Then it expects to see "Pre-Boil Amounts"Then it expects to see "Grain/Extract/Sugar"Then it expects to see "Hops"

After this things become a bit more variable.It now starts looking for combinations as this is where recipes generally start to include or exclude options dependant on your export options.

It now expects to see "Yeast" or "Extras"

It then expects to see "Water" which if not completed in the recipe will be 0.0 ppm anyway.

I'm actually not too sure on the Water part. (I don't have the full code on this computer). I may have removed a dependancy on the Water section.

Finally it looks for "Mash Schedule"

It will also pickup any recipe notes.

Can you please send me the recipe that was failing for you Fred ?

This tool was written to convert recipes that were published to brewing internet forums, specifically where users do not have Promash. I'd like to iron out this bug, as these users would not be able to re-export a recipe.

Check the text and if not present just proceed to the next item (refering to below)[size=-1]Then it expects to see "Style Guidelines" Then it expects to see "Recipe Specifics" Then it expects to see "Pre-Boil Amounts" Then it expects to see "Grain/Extract/Sugar" Then it expects to see "Hops" [/size]

Doc

After locating the Recipe name and verifying the Promash export header it looks initially for "Style Guidelines" or "Recipe Specifics" This allows for recipes that don't have Style Guidelines eg. experimental and the author has not chosen the AHA or BJCP Experimental category.

Recipes Specs must be there and it must then be followed by "Grain/Extract/Sugar"

I could make it skip to next if not found, but if there are no fermentables etc, then why bother with the conversion anyway ?

So I'm guessing your Promash export didn't have a Recipe Specs section. Send me the one that failed for you and I'll look into it further.