![]() Some of my recipes had a forward slash within the recipe name, in cases where there was more than one name typically used for the recipe.A proper degree symbol can be entered using Alt-0176 and replacing again fixes the issue. Replacing these fixes the issue.Īnother one looked like the degree symbol, but a little more elongated. ![]() They are more curved than the ones generated by my keyboard, when hitting Shift and the key next to Enter: ", which seem to be just called “Quotation Marks”. The ones I found include what’s typically known as the “Right Double Quotation Mark”. In parsing the ingredients, directions and notes, the script trips up when it encounters certain characters. Let me know if you would like more details. The script stopped whenever it encountered a recipe that didn’t have a photo attached in Paprika. I’ve identified what I think are some of the issues, but I know nothing about Python so may be mistaken, but I did have my son weigh in and he knows some Python. I’ve been playing with this for a lot of today and it’s not quite ready for me to move everything over to Obsidian. I’ve 833 recipes in Paprika that I’ve been wanting to migrate to Obsidian and the only way I had was manual cut and paste, which I’d never have time for, so thank you! I may update the templates at some point. The functionality requires the MetaEdit and Buttons plugins. I have added a button to the template file which allows you to edit the metadata but honestly it’s not much more work (or complexity) to just edit the metadata. I found about 1/4 of the recipes needed some tweaking, and I’m now in the habit of doing that when I add a recipe to Paprika. You’ll have to go through and check the ingredients in each recipe, but this is optional, the conversions will still work without it, just there’ll be less scaling functionality. As the ingredient conversion is still fairly simplistic as I didn’t have time to look into the AI option. ![]() Good to hear and Hadn’t had any response on this and just assumed it was a bit too niche for folks to want to I did have a look into cooklang and while I think it’s a really interesting project, the thought of manually converting all my 600+ recipes wasn’t really appealing. It’ll work pretty much out of the box and supports recipe scaling and hiding empty elements. It’s already looking pretty good, but it could be even better/more useful.Įventually I’d like to be able to import recipes from a page into a Markdown note, without the use of Paprika. I hope other recipe/cooking tech fans can help create an even better Markdown recipe manager using just YML frontmatter and Dataview/DataviewJS. I’ve also included a plain markdown template and a YML only template if folks don’t want to use Dataview/Obsidian. It should also be fairly straightforward to program this for other recipe managers as well. ![]() You can choose and edit the templates and make your recipes into whatever you want them to be. I’ve uploaded the results to a GitHub repo with a fairly decent set of instructions on how to use it. I decided to write a script to move my recipes into Markdown. That was, until I migrated my md notes recently to Obsidian and stumbled upon this cool thread with some really nice ideas and DataView demos. After trying out a bunch of different self-hosted options like Tandoor, I didn’t find anything I really liked, so was stuck still using it. I’ve been looking for a while at moving my recipe database out of Paprika Recipe Manager. ![]()
0 Comments
Leave a Reply. |