[kde-doc-english] [Bug 85885] kbabel: missing section in documentation for "6. Preferences"/"KBabel preferences"/"Sourcecode"

[Nicolas Goutte]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=85885         




------- Additional Comments From nicolasg snafu de  2005-12-29 14:35 -------
SVN commit 492260 by goutte:

I have now looked closer at the problem and I think I know the difference
between  PACKAGEDIR@ and  POFILEDIR@ for path patterns for source references
(The main difference is due to the Catalog Manager)
CCBUG:85885


 M  +2 -2      index.docbook  
 M  +11 -8     preferences.docbook  


--- branches/KDE/3.5/kdesdk/doc/kbabel/index.docbook #492259:492260
 @ -35,8 +35,8  @
 </authorgroup>
 
 
-<date>2005-12-28</date>
-<releaseinfo>3.5.1.02</releaseinfo>
+<date>2005-12-29</date>
+<releaseinfo>3.5.1.03</releaseinfo>
 
 <abstract>
 <para>
--- branches/KDE/3.5/kdesdk/doc/kbabel/preferences.docbook #492259:492260
 @ -988,7 +988,7  @
 <title>Dialog elements</title>
 
 <para>
-In the text edit <guilabel>Base folder for source code</guilabel>, you can set a
+In the edit line <guilabel>Base folder for source code</guilabel>, you can set a
 base folder where the source code of your project is. This defines the value of the variable
 <userinput> CODEROOT </userinput>, which is described below.
 </para>
 @ -1038,9 +1038,12  @
 
 <important><para>
 The variables <userinput> PACKAGEDIR </userinput> and <userinput> POFILEDIR </userinput> have similar
-meaning but not the same result. The variable <userinput> POFILEDIR </userinput> will work for every file,
-<userinput> PACKAGEDIR </userinput> might not.
-<remark>TODO: that is badly explained!</remark>
+meaning but not the same result. The variable <userinput> POFILEDIR </userinput>
+will always hold the folder of <acronym>PO</acronym> file,
+<userinput> PACKAGEDIR </userinput> might not. If the <acronym>PO</acronym> file was loaded
+by the help of the &catalogmanager; then <userinput> PACKAGEDIR </userinput> has only the part of
+the path, based on the <acronym>PO</acronym> base path defined for the &catalogmanager;
+<link linkend="preferences-project-folders">(see below)</link>.
 </para></important>
 
 <note><para>
 @ -1079,7 +1082,7  @
 </itemizedlist>
 
 <note><para>
-&kde; projects need one of the three first patterns.
+&kde; projects need typically the third pattern.
 The last pattern is typical for &GNU; projects, where the source references are related to
 the parent of the directory where the PO file is.
 </para></note>
 @ -1090,9 +1093,9  @
 <title>Creating New Path Patterns</title>
 
 <para>
-Even if normally the default path patterns should be enough, whatever
-the project is a &GNU; one (or structured like a &GNU; project) or
-if the project is for KDE.
+In most cases the default path patterns should be enough, whatever
+the project is for KDE (assuming that you have set the correct base directory)
+or if the project is a &GNU; one (or structured like a &GNU; project).
 </para>
 
 <note><para>