From d8f0b6da3fdb13eaab6349aac6db9d74eee72c7e Mon Sep 17 00:00:00 2001
From: Alain Reguera Delgado <alain.reguera@gmail.com>
Date: May 29 2011 03:33:25 +0000
Subject: Add Backends/Texinfo/texinfo_getChapterDir.sh.


---

diff --git a/Scripts/Functions/Help/Backends/Texinfo/texinfo_getChapterDir.sh b/Scripts/Functions/Help/Backends/Texinfo/texinfo_getChapterDir.sh
new file mode 100755
index 0000000..359e8f5
--- /dev/null
+++ b/Scripts/Functions/Help/Backends/Texinfo/texinfo_getChapterDir.sh
@@ -0,0 +1,50 @@
+#!/bin/bash
+#
+# texinfo_getChapterDir.sh -- This function outputs the entry's
+# chapter directory.
+#
+# Copyright (C) 2009, 2010, 2011 The CentOS Project
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or (at
+# your option) any later version.
+#
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+#
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+function texinfo_getChapterDir {
+
+    local ENTRY="$1"
+
+    # Verify documentation entry. Only the first documentation entry
+    # provided must be used. This is for those cases where the first
+    # documentation entry needs to be retrived from a list of entries.
+    ENTRY=$(echo $ENTRY | cut -d ' ' -f 1)
+
+    # At this point, we need to take a desition about documentation
+    # design, in order to answer the question: How do we assign
+    # chapters, sections and subsections automatically, based on the
+    # repository structure?  and also, how such design could be
+    # adapted to changes in the repository structure?
+    #
+    # One solution would be: represent the repository's directory
+    # structure as sections inside a chapter named `Directories' or
+    # something similar. Subsections and subsubsections will not have
+    # their own files, they all will be written inside the same
+    # section file that represents the repository documentation entry.
+    if [[ $ENTRY != '' ]];then
+        echo $ENTRY | cut -d / -f-8
+    fi
+
+}