This file is indexed.

/usr/share/bibledit-gtk/site/gtk/tutorials/notes/project-notes.html is in bibledit-gtk-data 4.9-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <link href="../../../bibledit.css" rel="stylesheet" type="text/css" /><!-- 

Copyright (©) 2003-2011 Teus Benschop and Contributors to the Wiki.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts.  A copy of the license is included in the section entitled "GNU
Free Documentation License" in the file FDL.

-->
    <title></title>
  </head>
  <body>
    <div id="menu">
      <ul>
        <li>
          <a href="../../../home.html">1 Bibledit</a>
        </li>
        <li>
          <a href="../notes.html">Notes</a>
        </li>
        <li style="list-style: none; display: inline">
          <hr />
        </li>
        <li>
          <a href="bible-notes.html">Bible notes</a>
        </li>
        <li>Project notes
        </li>
      </ul>
    </div>
    <div id="content">
      <h1>
        Project notes
      </h1>
      <h2>
        <a name="TOC-General" href="" id="TOC-General"></a>General
      </h2>
      <p>
        During the process of translation many notes will be made that related to the project.
      </p>
      <p>
        Project notes are stored in a database, and are independent of any Bible text. That is, whichever project is opened or closed, the notes remain the same.
      </p>
      <h2>
        <a name="TOC-Creating-and-editing-project-notes" href="" id="TOC-Creating-and-editing-project-notes"></a>Creating and editing project notes
      </h2>
      <h3>
        <a name="creatingandeditingprojectnotes" href="" id="creatingandeditingprojectnotes"></a>
      </h3>
      <p>
        To make a new project note press Ctrl+N.
      </p>
      <p>
        To edit an existing project note click on the blue reference(s) for that note.
      </p>
      <p>
        When creating a new note or editing an existing one, the project notes window splits up into two so as to make space for a couple of controls.
      </p>
      <p>
        Project notes can be deleted by clicking on the blue [delete] link.
      </p>
      <p>
        Some keyboard shortcuts help while editing notes. An example will show how: The user edits the text of a project. To make a new note, he presses Ctrl+N. He types some text in the note. If he wishes to change to category of the note, he presses Alt+A, then Enter to open the list of categories, then he makes a selection with Up Arrow or Down Arrow and presses Enter to confirm the selection. If he wishes to add some references, he pressed Alt+R and types some references. Alt+O saves the note, and takes the user back to where he was editing the text. Ctrl-I puts the text in italics, Ctrl-B makes it bold, and Ctrl-U underlines it.
      </p>
      <p>
        When a project note is being edited, the creator of the note can be retrieved through menu View / More information on current note. Other information about this note is visible there as well, like the date it was created, and when it was edited.
      </p>
      <p>
        Each note falls into a category. The various categories and the default category can be set in the <a href="https://sites.google.com/site/bibledit/gtk/reference/menu/menu-preferences/project-notes">preferences</a>.
      </p>
      <h2>
        <a name="TOC-Finding-project-notes" href="" id="TOC-Finding-project-notes"></a>Finding project notes
      </h2>
      <h3>
        <a name="findingprojectnotes" href="" id="findingprojectnotes"></a>
      </h3>
      <p>
        Menu / Edit / Find in Project notes (Alt+E, N) allows to do Simple searches in the Project notes.
      </p>
      <p>
        This tool searches exacty (except case sensitive) for the sequence of characters entered into the "Search for" box, punctuation marks and spaces included. Case sensitive can be switched on or off.
      </p>
      <h2>
        <a name="TOC-Navigating-to-the-references-of-a-note" href="" id="TOC-Navigating-to-the-references-of-a-note"></a>Navigating to the references of a note
      </h2>
      <h3>
        <a name="navigatingtothereferencesofanote" href="" id="navigatingtothereferencesofanote"></a>
      </h3>
      <p>
        Project notes usually have one reference. This is the one for which the note was created. But additional references can be added as well.
      </p>
      <p>
        These references are shown attached to each note.
      </p>
      <p>
        There are two ways to get these notes into the references window.
      </p>
      <p>
        1. Open a note to edit it. In the menu choose Edit - Get references from project note.
      </p>
      <p>
        2. Click on the blue word [references] of a note.
      </p>
      <p>
        As a result the references will be loaded in the references window. Once there they can be activated and the text belonging to that reference will appear in the text editor.
      </p>
      <h2>
        <a name="TOC-Transferring-text-from-the-text-editor-into-the-project-notes" href="" id="TOC-Transferring-text-from-the-text-editor-into-the-project-notes"></a>Transferring text from the text editor into the project notes
      </h2>
      <h3>
        <a name="transferringtextfromthetexteditorintotheprojectnotes" href="" id="transferringtextfromthetexteditorintotheprojectnotes"></a>
      </h3>
      <p>
        Many people have one project with the actual text, and a separate project for their project notes. There is a historical reason for doing so. This separate project may have checking questions, answers from native helpers, a history of different renderings, commentary support, notes following consultant checks, and so on.
      </p>
      <p>
        It would be a lot of work to copy and paste these notes into the project notes one verse at a time.
      </p>
      <p>
        The tool "Transfer text to project", under the Tools menu, helps you with this.
      </p>
      <p>
        It transfers all text that is in the currently opened project into the project notes.
      </p>
      <p>
        It takes a good while to do this.
      </p>
      <h2>
        <a name="TOC-Notes-overlapping-chapters" href="" id="TOC-Notes-overlapping-chapters"></a>Notes overlapping chapters
      </h2>
      <h3>
        <a name="notesoverlappingchapters" href="" id="notesoverlappingchapters"></a>
      </h3>
      <p>
        If project notes need to overlap the chapter boundaries, the reference can be manually entered like, for example: Luke 2:2-3:3. Bibledit will divide this into two parts: Luke 2 verse 2 to the end of the chapter, and Luke 3 verse 1 to 3.
      </p>
      <h2>
        <a name="TOC-Showing-notes" href="" id="TOC-Showing-notes"></a>Showing notes
      </h2>
      <h3>
        <a name="showingnotes" href="" id="showingnotes"></a>
      </h3>
      <p>
        The <a href="https://sites.google.com/site/bibledit/gtk/reference/menu/view/project-notes">settings for which notes to show and how</a> are in the View menu.
      </p>
      <h2>
        <a name="TOC-Exporting-notes" href="" id="TOC-Exporting-notes"></a>Exporting notes
      </h2>
      <h3>
        <a name="exportingnotes" href="" id="exportingnotes"></a>
      </h3>
      <p>
        Project notes can be exported into some formats.
      </p>
      <p>
        * Bibledit Notes version 3. This is the format used by the current version of Bibledit. In other words, notes exported through this option can be imported in Bibledit.
      </p>
      <p>
        * ScriptureNotes version 2.0. Notes exported in this format can be imported by Translation Notes Editor 6.0.
      </p>
      <p>
        To see how these formats looks, just export some text and open the exported text in a text editor.
      </p>
      <h2>
        <a name="TOC-Sharing-notes" href="" id="TOC-Sharing-notes"></a>Sharing notes
      </h2>
      <p>
        The notes that you make on your computer can be shared with other members of the team. These notes you make will then also be available to the members of the team, and the notes made by any member of the team will also become available to you.&nbsp;
      </p>
      <p>
        You can set the sharing up through the <a href="https://sites.google.com/site/bibledit/gtk/reference/menu/menu-preferences/dialog-remote-repository">Remote Repository Assistant</a>. Normally this assistant sets up project sharing. But it can also set up notes sharing. Just make the appropriate selection at the start of the assistant. It will be good to read the entire section about <a href="https://sites.google.com/site/bibledit/gtk/tutorials/collaboration">Collaboration</a> if you need to set it up, since it fully explains the technical details.
      </p>
      <p>
        Notes are stored in flat files, but selected from an index. If the index for some reason gets corrupted or out of sync, then you can recreate it by either deleting the index manually from directory ~/.bibledit/notes and then restarting Bibledit, or by setting the sharing up again through the remote repository assistant.
      </p>
      <p>
        Menu File - Project notes - Send / Receive to a manual sync of your notes with the remote repository. Normally the sync is done automatically, though, by default it is done every hour, but you can change this in the remote repository assistant.
      </p>
    </div>
  </body>
</html>