/usr/share/bibledit-gtk/site/gtk/tutorials/3-editing.html is in bibledit-gtk-data 4.6-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 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 | <!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="../tutorials.html">Tutorials</a>
</li>
<li style="list-style: none; display: inline">
<hr />
</li>
<li>
<a href="bibledit-for-windows-tutorial.html">Bibledit for Windows Tutorial</a>
</li>
<li>
<a href="checking.html">Checking</a>
</li>
<li>
<a href="collaboration.html">Collaboration</a>
</li>
<li>Editing
</li>
<li>
<a href="keyterms-tutorial.html">Keyterms</a>
</li>
<li>
<a href="merge-tutorial.html">Merging</a>
</li>
<li>
<a href="navigation.html">Navigation</a>
</li>
<li>
<a href="notes.html">Notes</a>
</li>
<li>
<a href="planning.html">Planning</a>
</li>
<li>
<a href="printing.html">Printing</a>
</li>
<li>
<a href="project.html">Project</a>
</li>
<li>
<a href="questions.html">Questions</a>
</li>
<li>
<a href="references.html">References</a>
</li>
<li>
<a href="related-verses.html">Related verses</a>
</li>
<li>
<a href="revert.html">Revert</a>
</li>
<li>
<a href="searching.html">Searching</a>
</li>
<li>
<a href="spelling.html">Spelling</a>
</li>
<li>
<a href="styles.html">Styles</a>
</li>
</ul>
</div>
<div id="content">
<h1>
Editing
</h1>
<h3>
<a name="TOC-Project" href="" id="TOC-Project"></a>Project
</h3>
<p>
Before any editing can be done, create a new <a href="https://sites.google.com/site/bibledit/gtk/tutorials/project">project</a> and add books to it. See also the <a href="https://sites.google.com/site/bibledit/gtk/reference/menu/file/project/project-properties">Project Properties</a> dialog. Or of there is an existing project, open it.
</p>
<h3>
<a name="save" href="" id="save"></a>Save
</h3>
<p>
There is no need to save the text, because Bibledit takes care of that.
</p>
<h3>
<a name="text" href="" id="text"></a>Text
</h3>
<p>
Standard Format Markers are markers that are put in the text to indicate the book, where a chapter starts, the verse, titles and so on.
</p>
<p>
A marker always starts with a backslash (\) at the beginning of a line of text in the editor. The most commonly used Standard Format markers are:
</p>
<pre>
\id Identifies the book
</pre>
<pre>
\mt major title (if only one level is used. If more than one used:)
</pre>
<pre>
\mt1 major title, level 1
</pre>
<pre>
\mt2 major title, level 2 (equal to secondary title \st, but \st is no longer in use)
</pre>
<pre>
\c chapter
</pre>
<pre>
\s section heading
</pre>
<pre>
\p paragraph
</pre>
<pre>
\v verse
</pre>
<p>
Here follows a part of the book of John.
</p>
<pre>
\id JHN
</pre>
<pre>
\mt2 The Gospel according to
</pre>
<pre>
\mt1 John
</pre>
<pre>
\c 1
</pre>
<pre>
\s The Word became flesh
</pre>
<pre>
\v 1 In the beginning was the Word, and the Word was with God, and the Word was God.
</pre>
<p>
Explanation of markers used.
</p>
<pre>
\id JHN
</pre>
<p>
Identifies the book as John
</p>
<pre>
\mt2 The Gospel according to
</pre>
<p>
A major title, level 2. When printed it will have a font just a bit smaller than \mt
</p>
<pre>
\mt1 John
</pre>
<p>
A major title, level 1. When printed it will have a big font suitable for such a title.
</p>
<pre>
\c 1
</pre>
<p>
Indicates that chapter one starts here.
</p>
<pre>
\s The Word became flesh
</pre>
<p>
This is a section heading, and will be printed in the text as a heading, usually in bold.
</p>
<pre>
\v 1 In the beginning was the Word, and the Word was with God, and the Word was God.
</pre>
<p>
This is the text of verse one.
</p>
<p>
More information on <a href="https://sites.google.com/site/bibledit/gtk/reference/usfm">USFM</a> is available.
</p>
<h3>
<a name="data" href="" id="data"></a>Data
</h3>
<p>
All project data is stored in the <a href="https://sites.google.com/site/bibledit/gtk/4-management/data">data directory.</a>
</p>
<h3>
<a name="undo" href="" id="undo"></a>Undo and Redo<br />
</h3>
<p>
As long as you stay in the same chapter, you can undo and redo any changes made. See menu Edit, or use the <a href="https://sites.google.com/site/bibledit/gtk/reference/keyboard-accelerators">keyboard accelerators</a>.<br />
</p>
<h3>
<a name="insertingbiblenotes" href="" id="insertingbiblenotes"></a>Inserting Bible notes
</h3>
<p>
All Bible notes can be inserted by choosing the appropriate style.
</p>
<p>
A <a href="https://sites.google.com/site/bibledit/gtk/reference/menu/menu-none/insert-footnote-endnote-crossreference">new window</a> will come up, where you can set what will be inserted.
</p>
<p>
The numbering can be set to automatic, or no numbering at all, or a certain character.
</p>
<p>
Further you can set whether to automatically insert the current reference in the footnote. If you do insert it, then you can set whether to include the chapter number, and the verse number, and what the separator between them will be. A suffix can be entered too. It will show how this is going to look in the text.
</p>
<p>
The size of the text entry or entries can be set using the "Size" arrows.
</p>
<p>
It is possible to save a certain footnote configuration in a template. The "New" button will make a new template, and the "Delete" button will delete the current one. If no template name is given, the default one will be used. Data is saved in a template only on pressing the "Ok" button.
</p>
<p>
The same things apply to endnotes and crossreferences.
</p>
<h3>
<a name="changingbiblenotes" href="" id="changingbiblenotes"></a>Changing Bible notes
</h3>
<p>
A Bible note can be a footnote, an endnote, or a crossreference. This type can be changed. To do that, place the cursor somewhere in the note to be changed. Choose menu Edit / Bible note, and set the new type, and then press OK.
</p>
<p>
The numbering of the note can be changed in the same way. One can for example change from automatic to manual numbering, and vice versa.
</p>
<h3>
<a name="pictures" href="" id="pictures"></a>Pictures
</h3>
<p>
Bibledit has good support for the \fig marker. Pictures are inserted manually, following the USFM standard.
</p>
<p>
At printing time, Bibledit looks for the picture file in various ways. If an absolute path is given, then it will look for the file there. If a relative path is given, it first looks in <<a href="https://sites.google.com/site/bibledit/gtk/4-management/data">data directory</a>>/pictures, then among Bibledit's template files.
</p>
<p>
According to the USFM standard, the picture size can be set to "col" or to "span". In addition to that, if the picture size has not been set, Bibledit uses the intrinsic size of the picture. The "span" property is not yet supported at this time. All other properties are.
</p>
<h3>
<a name="view" href="" id="view"></a>View
</h3>
<p>
The text is displayed in formatted form. This means that the raw USFM code is hidden, and instead the code is formatted and is displayed in that form.
</p>
<p>
If the user wishes to view or edit the raw USFM code, there is a setting for this in menu View / USFM code. If this menu entry is ticked, the raw USFM code can be edited. If the tick is removed it reverts to the normal formatted view.
</p>
<p>
In the formatted view, the stylesheet will determine what part of the text is formatted and what is left unformatted. If the stylesheet contains all the styles in the document, then everything will be formatted. If a style is in the document, but not in the stylesheet, than that particular style will be shown unformatted, but the rest is still formatted. In this way, by using various stylesheets with more or less styles, Bibledit can be more or less formatted. In this way the user has a lot of flexibility to fine-tune the view. Some styles will always be unformatted.
</p>
</div>
</body>
</html>
|