Skip to content

Commit 0199c3b

Browse files
committed
update for consistent format
1 parent a86026b commit 0199c3b

File tree

8 files changed

+312
-283
lines changed

8 files changed

+312
-283
lines changed

RM -Change source for citation/ReadMe.txt

Lines changed: 50 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -120,49 +120,53 @@ Run the Python installer selecting all default options.
120120
=========================================================================DIV80==
121121
NOTES
122122

123-
* All interactions with the utility are through the RM-Python-config.ini file
124-
and the command line console window.
125-
The RM-Python-config.ini file just give the location of the database to
126-
modify. The same RM-Python-config.ini file can be shared with other utility
127-
applications such as TestExternalFiles and GroupFromSQL.
128-
129-
* Information that the user enters in the command window is checked before
130-
it is used. It is unlikely that random data would be accepted by
131-
the utility.
132-
133-
* The utility asks for the name of the citation to change and the source
134-
that it should use. In both cases, only enough of the name needs to be
135-
entered to make it unique among all citations for all sources.
136-
It is suggested that you copy and paste from the RM source edit window.
137-
There is no need to manually type input.
138-
One may start the name entry with a % char and it will be used as the
139-
standard 'SQL Like' wild card.
140-
If the full citation name is not unique, then as a workaround, you
141-
could add some text to the citation name of the citation you want
142-
to modify to make the name unique.
143-
144-
* Checks made by the utility:
145-
1- User is asked for the citation name of the citation to modify.
146-
a) the name must be found.
147-
b) the name must be unique among all citations for all sources.
148-
You will be made aware of problems.
149-
2- User is asked for the source that is to be used as the new parent of
150-
the citation.
151-
a) the source name must be found.
152-
b) the source name must be unique.
153-
c) the existing source used by the citation and the new source
154-
specified must both use the same source template.
155-
You will be made aware of problems.
156-
157-
===========================================DIV50==
123+
=========-
124+
All interactions with the utility are through the RM-Python-config.ini file
125+
and the command line console window.
126+
The RM-Python-config.ini file just gives the location of the database to
127+
modify. The same RM-Python-config.ini file can be shared with other RM
128+
utilities.
129+
130+
=========-
131+
Information that the user enters in the command window is checked before
132+
it is used. It is unlikely that random data would be accepted by
133+
the utility.
134+
135+
=========-
136+
The utility asks for the name of the citation to change and the source
137+
that it should use. In both cases, only enough of the name needs to be
138+
entered to make it unique among all citations for all sources.
139+
It is suggested that you copy and paste from the RM source edit window.
140+
There is no need to manually type input.
141+
One may start the name entry with a % char and it will be used as the
142+
standard 'SQL Like' wild card.
143+
If the full citation name is not unique, then as a workaround, you
144+
could add some text to the citation name of the citation you want
145+
to modify to make the name unique.
146+
147+
=========-
148+
Checks made by the utility:
149+
1- User is asked for the citation name of the citation to modify.
150+
a) the name must be found.
151+
b) the name must be unique among all citations for all sources.
152+
You will be made aware of problems.
153+
2- User is asked for the source that is to be used as the new parent of
154+
the citation.
155+
a) the source name must be found.
156+
b) the source name must be unique.
157+
c) the existing source used by the citation and the new source
158+
specified must both use the same source template.
159+
You will be made aware of problems.
160+
161+
=========-
158162
REPORT_FILE_DISPLAY_APP
159163

160164
Option to automatically open the report file in a display application.
161165
The included ini sample file has this option activated and set to use Windows
162166
NotePad as the display app. It can be deactivated by inserting a # character
163167
at the start of the line. Your favorite editor may be substituted.
164168

165-
===========================================DIV50==
169+
=========-
166170
RM-Python-config.ini (the config file)
167171

168172
If there are any non-ASCII characters in the config file then the file must be
@@ -185,39 +189,29 @@ file line- REPORT_FILE_DISPLAY_APP
185189

186190
If no report file is generated, look at the black command
187191
console window for error messages that will help you fix the problem.
188-
There is probably something wrong with the config file line-
189-
REPORT_FILE_PATH
192+
There may be something wrong with the config file line- REPORT_FILE_PATH
190193

191-
=========-
192-
Error message:
194+
If the black console windows displays the message-
193195
RM-Python-config.ini file contains a format error
194-
195-
The problem is as stated, the solution may be harder to determine.
196-
Start over with the supplied config file and make sure that works, Then make your
197-
edits one by one to identify the problem.
198-
You may want to look at- https://en.wikipedia.org/wiki/INI_file
199-
200-
A reason that report file cannot be generated is if the specified REPORT_FILE_PATH
201-
cannot be created.
202-
The default value in the supplied config file should always work.
196+
See the section below.
203197

204198
If no report file is generated and the black command console window closes
205199
before you can read it, try first opening a command line console and then
206200
running the exe or py file from the command line. The window will not close
207201
and you'll be able to read any error messages.
208202

203+
=========-
204+
Error message:
205+
RM-Python-config.ini file contains a format error
206+
207+
Start over with the supplied config file and make sure that works, Then make your
208+
edits one by one to identify the problem.
209+
You may want to look at- https://en.wikipedia.org/wiki/INI_file
209210

210211
=========================================================================DIV80==
211212
TODO
212213
* ?? what would you find useful?
213214

214-
* Do you have citations in different sources with the same citation name?
215-
That situation will prevent you from using this app.
216-
I could add a workflow where the utility will first ask for the source
217-
and then ask for a citation name that is used by that source, but
218-
it increases the effort for a situation that may not be common, especially
219-
as there is a workaround: temporarily change one of the citation names.
220-
221215

222216
=========================================================================DIV80==
223217
Feedback

RM -Change source template/ReadMe.txt

Lines changed: 13 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -508,7 +508,6 @@ If there are changes that you did not want, make another copy of your main
508508
database file and copy it to the working folder and try again.
509509

510510

511-
=========================================================================DIV80==
512511
=========================================================================DIV80==
513512
NOTES
514513

@@ -618,7 +617,7 @@ field (and vice versa)
618617
* NULL on the left side (old source template) means that the field on right
619618
side will be empty but correctly initialized. Must be used when adding a new
620619
field but without moving old data to it.
621-
In RM v9.1.3, an uninitialized data field will not behave as expected in
620+
In RM v10, an uninitialized data field will not behave as expected in
622621
the footnote sentence language. This may get fixed.
623622

624623
* NULL on right side (destination) means the data on left side field will not be
@@ -714,35 +713,33 @@ at the start of the line.
714713
=========================================================================DIV80==
715714
Troubleshooting:
716715

717-
===========-
716+
=========-
718717
No Report File displayed
719718

720719
If the report is created, but not displayed, check the config
721720
file line- REPORT_FILE_DISPLAY_APP
722721

723722
If no report file is generated, look at the black command
724723
console window for error messages that will help you fix the problem.
725-
There is probably something wrong with the config file line-
726-
REPORT_FILE_PATH
724+
There may be something wrong with the config file line- REPORT_FILE_PATH
727725

728-
===========-
729-
Error message:
726+
If the black console windows displays the message-
730727
RM-Python-config.ini file contains a format error
731-
732-
The problem is as stated, the solution may be harder to determine.
733-
Start over with the supplied config file and make sure that works, Then make your
734-
edits one by one to identify the problem.
735-
You may want to look at- https://en.wikipedia.org/wiki/INI_file
736-
737-
A reason that report file cannot be generated is if the specified REPORT_FILE_PATH
738-
cannot be created.
739-
The default value in the supplied config file should always work.
728+
See the section below.
740729

741730
If no report file is generated and the black command console window closes
742731
before you can read it, try first opening a command line console and then
743732
running the exe or py file from the command line. The window will not close
744733
and you'll be able to read any error messages.
745734

735+
=========-
736+
Error message:
737+
RM-Python-config.ini file contains a format error
738+
739+
Start over with the supplied config file and make sure that works, Then make your
740+
edits one by one to identify the problem.
741+
You may want to look at- https://en.wikipedia.org/wiki/INI_file
742+
746743
===========-
747744
Error Message:
748745
Tried to create duplicate Name in XML.

RM -Citation Sort Order/ReadMe.txt

Lines changed: 19 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,7 @@ Run the Python installer selecting all default options.
120120
=========================================================================DIV80==
121121
NOTES
122122

123+
=========-
123124
CitationSortOrder can change the sort order for citations attached to Person,
124125
Names, and Facts.
125126
Currently, this utility will not change the sort order of citations attached to
@@ -129,35 +130,41 @@ This utility only changes the database table: CitationLinkTable and within
129130
it, only the SortOrder column..
130131

131132

133+
=========-
132134
Due to lack of support in the RM app, the modified sort order is not utilized
133-
in the "slide in" workflow for facts or in reports generated by RM.
135+
in the "slide in workflow" for facts or in reports generated by RM.
134136

135137

138+
=========-
136139
Use of this utility may be productively combined with the use of a global
137140
re-ordering SQL script developed by Tom Holden and Jerry Bryan.
138141
https://sqlitetoolsforrootsmagic.com/forum/topic/sorting-the-order-of-rm9-citations/
139142

140143

144+
=========-
141145
Note that after reordering, newly added citations will appear at the top
142146
of the list as they will have a SortOrder number of 0.
143147
This contrasts with behavior seen before reordering where the citations are shown
144148
in "order entered" sequence because all records are added with a SortOrder number of 0.
145149
Use this app to make desired changes.
146150

147151

152+
=========-
148153
Updating the sort order of a set of citations while the database is open in
149154
RM works OK. However, the citation lists do not have a refresh button, so,
150155
you'll need to navigate away from the modified sort order citation list and then
151156
return to it to see the new sort order.
152157

153158

159+
=========-
154160
To revert all citation sort order modifications made by this utility, simply
155161
change the sort order column to all zeros.
156162
UPDATE CitationLinkTable SET SortOrder = 0;
157163
This will change the sort order in RM v10 to "order entered", which is
158164
the default.
159165

160166

167+
=========-
161168
RM-Python-config.ini (the config file)
162169
If there are any non-ASCII characters in the config file then the file must be
163170
saved in UTF-8 format, with no byte order mark (BOM).
@@ -169,6 +176,7 @@ File format is an option in the "Save file" dialog box in NotePad.
169176
config file path names may be absolute or relative to the current directory.
170177

171178

179+
=========-
172180
REPORT_FILE_DISPLAY_APP
173181
Option to automatically open the report file in a display application.
174182
The included ini sample file has this option activated and set to use Windows
@@ -190,27 +198,25 @@ file line- REPORT_FILE_DISPLAY_APP
190198

191199
If no report file is generated, look at the black command
192200
console window for error messages that will help you fix the problem.
193-
There is probably something wrong with the config file line-
194-
REPORT_FILE_PATH
201+
There may be something wrong with the config file line- REPORT_FILE_PATH
202+
203+
If the black console windows displays the message-
204+
RM-Python-config.ini file contains a format error
205+
See the section below.
206+
207+
If no report file is generated and the black command console window closes
208+
before you can read it, try first opening a command line console and then
209+
running the exe or py file from the command line. The window will not close
210+
and you'll be able to read any error messages.
195211

196212
=========-
197213
Error message:
198214
RM-Python-config.ini file contains a format error
199215

200-
The problem is as stated, the solution may be harder to determine.
201216
Start over with the supplied config file and make sure that works, Then make your
202217
edits one by one to identify the problem.
203218
You may want to look at- https://en.wikipedia.org/wiki/INI_file
204219

205-
A reason that report file cannot be generated is if the specified REPORT_FILE_PATH
206-
cannot be created.
207-
The default value in the supplied config file should always work.
208-
209-
If no report file is generated and the black command console window closes
210-
before you can read it, try first opening a command line console and then
211-
running the exe or py file from the command line. The window will not close
212-
and you'll be able to read any error messages.
213-
214220

215221
=========================================================================DIV80==
216222
TODO

RM -Color from Group/ReadMe.txt

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -216,11 +216,13 @@ clearing colors in multiple color code sets.
216216
=========================================================================DIV80==
217217
NOTES
218218

219-
* Updating the colorization of a group while the database is open in RM
219+
=========-
220+
Updating the colorization of a group while the database is open in RM
220221
works OK. However, RM will not refresh the screen based on an external update.
221222
So, switch screens and then return to see the updated color coding.
222223

223-
* On some occasions, the utility report file will display a "Database
224+
=========-
225+
On some occasions, the utility report file will display a "Database
224226
Locked" message. In that case, close RM and re-run the utility, then re-open
225227
RM. It's not clear why this sometimes happens, but it is rare.
226228
No database damage has ever been seem after many hundreds of uses.
@@ -229,17 +231,20 @@ No database damage has ever been seem after many hundreds of uses.
229231

230232
Less important notes.
231233

232-
* RM-Python-config.ini (the config file)
234+
=========-
235+
RM-Python-config.ini (the config file)
233236
If there are any non-ASCII characters in the config file then the file must be
234237
saved in UTF-8 format, with no byte order mark (BOM).
235238
The included sample ini file has an accented ä in the first line comment to
236239
force it to be in the correct format.
237240
File format is an option in the "Save file" dialog box in NotePad.
238241

239-
* This utility only changes the database's PersonTable.
242+
=========-
243+
This utility only changes the database's PersonTable.
240244
If I add the feature of renaming colors, that will affect the Config table.
241245

242-
* This utility will, if so configured, modify a pre-existing color coding
246+
=========-
247+
This utility will, if so configured, modify a pre-existing color coding
243248
that may be important to you. Take care when assigning the actions in the
244249
config file.
245250

RM -Convert Fact/ReadMe.txt

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -315,27 +315,25 @@ file line- REPORT_FILE_DISPLAY_APP
315315

316316
If no report file is generated, look at the black command
317317
console window for error messages that will help you fix the problem.
318-
There is probably something wrong with the config file line-
319-
REPORT_FILE_PATH
318+
There may be something wrong with the config file line- REPORT_FILE_PATH
319+
320+
If the black console windows displays the message-
321+
RM-Python-config.ini file contains a format error
322+
See the section below.
323+
324+
If no report file is generated and the black command console window closes
325+
before you can read it, try first opening a command line console and then
326+
running the exe or py file from the command line. The window will not close
327+
and you'll be able to read any error messages.
320328

321329
=========-
322330
Error message:
323331
RM-Python-config.ini file contains a format error
324332

325-
The problem is as stated, the solution may be harder to determine.
326333
Start over with the supplied config file and make sure that works, Then make your
327334
edits one by one to identify the problem.
328335
You may want to look at- https://en.wikipedia.org/wiki/INI_file
329336

330-
A reason that report file cannot be generated is if the specified REPORT_FILE_PATH
331-
cannot be created.
332-
The default value in the supplied config file should always work.
333-
334-
If no report file is generated and the black command console window closes
335-
before you can read it, try first opening a command line console and then
336-
running the exe or py file from the command line. The window will not close
337-
and you'll be able to read any error messages.
338-
339337

340338
=========================================================================DIV80==
341339
TODO

0 commit comments

Comments
 (0)