You can export your favorite recipes to HTML and print them out with your favorite browser, if you want to.
However you may find it more easy to use AnyMeal instead of a shelf full of cookbooks, if you want to find the recipes you can do with the ingredients you have.
You may think that you don't need so many recipes as you may only be able to use about forty thousand in a lifetime.
Compare it to your phone-book. Of course you'll never need all the phone numbers it contains. But for most entries you cannot rule out that one day you may need that particular one.
The more recipes you have, the less likely you'll fail to find the appropriate recipe for a given occasion.
mealMasterCompiler.o(.text+0x521):/home/engjw/Documents/AnyMeal/anymeal/mealMasterCompiler.cpp:97: undefined reference to `mealMasterlex()'
cd anymeal
flex -PmealMaster -omealMaster.cc mealMaster.ll
cd ..
make again, to finish compilation of the program.
cd anymeal
for i in *.ui; do sed 1s/3\.3/3.2/ $i > $i.tmp; mv $i.tmp $i; done
cd ..
This should only be of concern to you, if you want to modify the .ui-files. Otherwise the built sources will be included in the software-package already.
Find out the common base-directory of the docbook-scripts. If the package-name of the docbook-scripts f.e. was docbook-xsl-stylesheets-1.64.1-71.noarch.rpm, you'll find the location of the docbook-scripts by executing:
rpm -ql docbook-xsl-stylesheets | grep -w "docbook\.xsl"
/usr/share/xml/docbook/stylesheet/nwalsh/1.64.1/fo/docbook.xsl
/usr/share/xml/docbook/stylesheet/nwalsh/1.64.1/html/docbook.xsl
/usr/share/xml/docbook/stylesheet/nwalsh/1.64.1/manpages/docbook.xsl
/usr/share/xml/docbook/stylesheet/nwalsh/1.64.1/xhtml/docbook.xsl
Now you should be able to configure AnyMeal by specifying the base-directory. In this example it would work like this:
./configure --with-docbook-dir=/usr/share/xml/docbook/stylesheet/nwalsh/1.64.1
Note that the following steps where tested under SuSE 10.0. It may be a bit different on other distributions of GNU/Linux.
su # Log in as super-user.
mysql_install_db # Setup database-files.
chown -R mysql.mysql /var/lib/mysql/mysql # Change owner of the files.
/etc/init.d/mysql start # Start mysql-daemon
insserv mysql # Add mysql-daemon to the boot-up scripts.
mysqladmin password mypassword # Sets super-user password of database
exit # Log out from super-user mode.
You can change the password of the database administrator by doing
su # Log in as super-user.
mysqladmin -p password mynewpassword # Change password.
exit # Terminate super-user session.
AnyMeal can read Mealmaster files encoded in UTF-8 as well as in ISO-8859-1. You need to specify the proper encoding in the import dialog.
Note, that erroneous recipes are exported in UTF-8. AnyMeal only supports exporting recipes in UTF-8 at the moment.
In case you are not sure about the encoding of your file, you can use the command-line tool file to detect it:
file <filename>
UTF-8 is the recommended encoding on Unix/Linux platforms
AnyMeal should be able to display characters of any language supported by KDE/X11/Qt.
Also note, that Qt is able to render AnyMeal in reverse mode:
./anymeal --reverse
Execute the locale-command, to get information about the country-, language- and encoding-settings of your Linux-system:
locale
You can f.e. add the option
FOP_OPTS=-Xmx128m
At the moment fop's memory consumption forbids compiling cookbooks with more than a couple of hundred recipes even on recent computers.
for i in *.zip; do unzip "$i"; done
There is a bug in the Qt/KDE integration patches to Qt in SuSE 9.3 which is causing third-party applications to fail to work properly.
Its easy to duplicate and show and is a problem in the patch to redirect Qt QMessageBox static methods to KDE message boxes.
For more information see here or here.
You have to execute anymeal from the command line after setting an environment variable provided by SuSE to fix this.
export QT_NO_KDE_INTEGRATION=1
anymeal
Fehler: Error applying XSL-script "/usr/opt/kde3/share/apps/anymeal/scripts/docbookToFo.xsl":
XSLT Error: The variable 'id' is not defined.
Source tree node: article.
(file:///usr/share/xml/docbook/stylesheet/nwalsh/current/fo/component.xsl,
line 605, column 28.)
Simply edit the block starting at line 605 of the file component.xsl and replace
<fo:block id="{$id}">
<xsl:call-template name="article.titlepage"/>
</fo:block>
<!-- <fo:block id="{$id}">
<xsl:call-template name="article.titlepage"/>
</fo:block> -->
Besides: AnyMeal is making use of flex and self-implemented finite-state-machines for fast parsing.
It is also using the advanced XML-libraries of the Apache software-foundation. If you do a comparison, you'll note, that AnyMeal still is faster than most other applications.
Please file a support-request or bug-report (as appropriate) on the tracker's-page.
I'll try to answer your request as quickly as possible.