From d271fd3c055d7978ae4e3bf9cea533b0c3996435 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Tue, 12 Feb 2013 11:58:42 +0000 Subject: [PATCH] Mentioned xorriso-tcltk in the online FAQ --- libisoburn/trunk/doc/faq.wiki | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/libisoburn/trunk/doc/faq.wiki b/libisoburn/trunk/doc/faq.wiki index b3d15e13..03c7a8b0 100644 --- a/libisoburn/trunk/doc/faq.wiki +++ b/libisoburn/trunk/doc/faq.wiki @@ -6,7 +6,6 @@ Please post your questions to ---------------------------------------------------------------------------- '''Content:''' ----------------------------------------------------------------------------- Burning: @@ -234,6 +233,8 @@ The xorriso API encapsulates calls to libisofs, libburn, and libisoburn. An alternative to the xorriso C API is xorriso dialog mode. [#xorriso_dialog_mode See below.] +The script xorriso-tcltk demonstrates this approach. It is part of the +libisoburn release tarball and of the GNU xorriso tarball. The known existing GUIs [http://www.xfce.org/projects/xfburn/ Xfburn], [http://projects.gnome.org/brasero/ Brasero], @@ -285,6 +286,9 @@ xorriso's stdin and stdout. This is more efficient than forking xorriso every now and then to perform various commands in order to complete complex tasks like image size prediction. +The script xorriso-tcltk demonstrates this approach. It is part of the +libisoburn release tarball and of the GNU xorriso tarball. + ===== Why is every second release missing ? ===== #version_numbers Releases have an even third version number. Like 0.5.6 or 1.0.4.