There is a brief description of this format in the section of the Paprika Recipe Manager User Guide on importing recipes. This just seemed too painful to do at the same time I was trying to learn about the YAML file format. But every experiment trial you made would involve connecting up your iOS device to your computer, using iTunes file sharing to transfer over the ".yml" files and then using the import function to check whether you'd gotten things right and the way you want. You can also batch import your own recipes directly into the iOS version of the app, using the file structure keywords I've described in this post. Certainly you can do that and spend time reformatting each recipe by hand in any of these software applications. Also, I never found a way to bulk import your own recipes the way you can in Paprika in MacGourmet or any other major recipe manager software - and I don't mean that you can't copy and paste in recipes one by one in these apps. MacGourmet, which is a very nice desktop Mac package, but doesn't have the same easy sync and integration with iOS devices. (Hope the formatting works, because I'm not at my computer, so I'm copying the text from the Mail Archive post I sent to the Mac-Access list a year ago as part of a reply to a question about Paprika vs. I'll paste in a sample recipe for an example. This is just one way to combine files into a single file that I name "recipes1.yml" you don't have to do it this way: I perform this in Terminal in the directory that holds a group of my recipe files in TXT format. Linux users will recognize the "cat" command to concatenate (put together) multiple files into a single file. Then I used the Terminal command line to put all the recipe TXT files in a given folder into a single ".yml" file that I imported. So the way I handled the import was to start with my recipes as plain text files with the specified format. I personally don't like importing these file by file, nor do I find the ".yml" extension a natural one to use. The easiest way to check this out is to try importing a single text recipe, and then examine the result and determine whether there are changes you want to apply before you import all your recipes. If you only import a single recipe at a time, it doesn't matter whether you precede the name with a hyphen and a space or not. If you plan to import multiple recipes at once within a single file, then the "name" keyword has to be preceded by a hyphen and a space, so the import process can determine where new recipes start. Of course, your recipes would all be uncategorized, and the ingredients and directions wouldn't be separated or appear under the sections for ingredients and directions, but this would be a valid import format. You could probably just have a "name" keyword, and then everything else (ingredients, directions, etc.) under a text block for "notes" and import your recipes. You don't have to use all the available keywords for recipes, and the order you list them also doesn't matter, as long as they follow the name. You can have multiple categories listed, like:Ĭategories: For the recipe categories keyword argument(s), enclose your categories between left and right square brackets. Then, the subsequent lines of text until the next line with a keyword will all be part of the text block associated with that keyword. For blocks of text, such as a list of ingredients, directions, or notes, use a colon, space, and then a vertical line character (Shift-Backslash or "|", where the backslash is the rightmost key below "delete" and above "return" on an English language input keyboard). Keywords like "name" and "servings" are followed by a colon and a space, then the text argument. You need to use text files and name them with a ".yml" extension for YAML format before you import. Paprika uses the file extension type to recognize the importing format.
0 Comments
Leave a Reply. |